Sorry if I made it wrong, but I believe creating separate task would be better in this case, to not spam about not related discussion on to the parent task, additionally I have no right to create a new task, so sub-task was sort of HACK for me while not spamming because I am still not member of Community.
This is created based on question above and it it sort of off topic discussion, but since many of features of Phabricator (important for me and other) are on the way for few years already I would like to remind about one the the modules of Phabricator - Fund.
Currently initiatives can be done by administrators only, but what if this would be the way how community could support some of the features they really need to have faster then what it is put now on the actual road map or even star map. Like for example this is planned for Phriction v3 from what I see it is waiting in stack to be done for about a year+. Anyways.
This discussion might possible cover some parts of the T12681 or T12904, but I see them as a different approach. Instead of one company / group paying for the feature they need (and others enjoy that clapping hands) I believe there could be a different approach of funding, with the fund module I mentioned. Yes I know fund itself is a prototype application, only mentioned in Starmap with one key sentence:
We have no specific plans around Fund.
How this could work?
As with many other features / bugs and etc. we have a related task this this one. Then we have some subscribers where some of them are sort of interested into this and some even maybe want this or that ASAP. Of course when it comes to paying money for things to happen faster most just hide in the woods while bloody tax collectors are passing by (trying to make my story more interesting here).
But hell I believe that there would be community members willing to pay buck or two to reach some funding level where actual changes would happen, like increase in priority and maybe more.
So at start there could be an action on manifest task panel on the right near subscribe Make Initiative or something like that, which if used then would create a child object on Fund which would let all the community to fund this and support somehow. Then when initiative is created it could be seen on task and instead of Make Initiative there would be something like Fund This. Of course this sort of working would require quite a few changes, but I believe it would make a difference and at start it could be done partly manually with the existing Fund only it would need you to manually create the initiatives.
Anyways next would be funding levels / targets. When for example certain funding level for issue/ task would reach, Phabricator guys would see this is what is sort of important for community and you increase a priority for it - but I mean increase it for real. It depends of course on the issue / task but I guess that could be defined some how and maybe a starting point would be this:
- 150 buck level initial rewiew.
- 300 buck level make deeper analysis with expected release date based on current situation.
- 1500 buck level put higher priority (i mean really higher not just for eyes)
- 3000 move from Starmap to Roadmap or other major change in the planning.
Levels are imaginary, but the idea first for you to check how much funding additionally it is needed to get it done like in a few months or so and then additional levels to get it done faster. This is a whole scratch idea, I believe there could be some very similar points discussed with your Supporting Mana changes, but this is also sort of different approach.