In T12900#228746, @epriestley wrote:

Only you and users who have permission to edit <Blog Name> can see this draft until it is published. Use "Publish" to publish this post.

...would that resolve things in your case? Or does the rule we actually implement not work as well as "only the author" in your use case?

I also had the same problem and solved in the same way!...

2. Why is there a 2 in the middle of all that? https://xkcd.com/1530/

In T11669#197945, @chad wrote:

It's always felt like 10% unpredictable to me, but I haven't tried it in a while.

Among other issues, arrows are, e.g., ambiguous in this case:

...
|          |   |   B    |
+----------+   +--------+
+----------+  
|    A     |   +--------+
|          |   |   C    |
|          |   +--------+
+----------+
+----------+   +--------+
|          |   |   D    |
...

If you click "Move Right" on "Panel A", does it move between panels B and C or between panels C and D?

In T11775#197941, @epriestley wrote:

even sometime seems to me not properly working

If this isn't working properly, please file a bug report with complete reproduction steps we can use to reproduce the issue. See Contributing Bug Reports.

As said in Q501 it will be useful to have some components (e.g. an administrative panel) that appear on top of all the dashboards.

In T5051#156552, @chad wrote:

...
This task will be re-scoped to just being about burn down charts for milestones.

In my personal opinion adding a CC that cannot see the task is an error and like this should be treated, meaning ux should just report as error when try to save it. It is important that ux reports it since it can be overlooked by the person changing the task.

I understand the point, but then, what do you think about "automatically" assign users to a space depending on the autentication they used to login? (i.e. only who autenticated with LDAP will belong to internal users)

Just to add: in a big organizations Spaces can be used to divide different legal entities in a group (or big departments).
With this use most probably the majority of the users will belong just to one space, and they will just see the (default) "public" space and their own one. That means that in this case the majority of the users will not even need the switch, but just the possibility to configure the default space for new objects to their own one (not the default "public" space).
The user configurable parameter for the default space for the new objects creation can be anyway a first step in implementing then the full functionality of Space switching.

Missed in the first instance this nice video: http://www.targetprocess.com/kanban/

This feature will for example solve the problem of visualizing all-together the tasks coming from different subprojects, without having to visualize the sub-tasks in each sub-project or alternatively having to have all of them mixed up in one (single dimension) Kanban.

The point is to give a more powerful visualization to Phabricator Kanban.

I didn't notice. And I have surely not the latest version of Phabricator! :)
At this point the question is if the problem will arise during the upgrade, or it is managed in some way?

In my installation I even used the "voting" feature in a gamification mechanism in order to increase the willingness to answer questions.
The points you get for an answer are multiplied by the number you get from the voting (+1). In my case I also give points for questions (even if a bit less) since I want to spread the utilization of this nice application.

There is no "problem", in my case just the idea to add some badges to "award" people that use Ponder (with a complex logic of points given based on number of questions, answers, like, dislike, frequency of use, etc.)

Can you please articulate other options in order to integrate Phabricator with other tools (apart from rewriting everything inside it) in order to give the user something like a portal (as it appears phabricator itself to be designed to)?
I'm genuinly interested in them

If someone will be able to get administrator rights I think there will be a lot of "holes" to get in other than an HTML panel, and a lot more damage possible than just impersonating a user.

Regarding UI: what about the possibility (not requirement) to assign a user a "default project" and a project a "default space" in order to have them "pre-compiled" when new entities are created by the user? (in big organizations often PM, users and developers belongs to one project only or work mainly for one at a time)

"Alt" and later with alt continuously pressed "9" "6" (on the keypad) will do the job if needed

Created pull request: https://github.com/phacility/phabricator/pull/734