Page MenuHomePhabricator

Implement a MRO for the tag (project in a manifest task)
Closed, DuplicatePublic

Description

I wish there were some king of method resolution order for displaying the project "tags".

Screenshot from 2015-05-18 21-56-40.png (255×1 px, 45 KB)

In this example T33 was created first the T34-36 as subtasks of T33.
And as you can see the tags are not consistently ordered

Short term :

  • If they can be classed by alphabetical order

Long term :

  • give the possibility to boost (ie a bugs project will appear first)

Event Timeline

tycho.tatitscheff raised the priority of this task from to Needs Triage.
tycho.tatitscheff updated the task description. (Show Details)

Well @chad the short term isnt' about a custom field or so.
It is just that I find more consistant to get the tag in a fixed order instead of random one. No user interface change.

We don't generally build features like that, that is as a one-off request. We look at a collection of feature requests and plan a path forward that solves many problems with a scalable system. That is T418.

Also, check out https://secure.phabricator.com/book/phabcontrib/article/feature_requests/. We prefer feature requests just state problems and not solutions, mostly that there may already be a solution to your problem or the solution we want in the upstream may differ from your suggestion.

All my fault. I m gonna read this and impove my future requests (More Arez Comming ! Fear).
I was just surprised that this task was merge into "Integrate custom field for XXXX".

But now, It's all clear !

We should probably rename that task at this point.