"In Development" status tied to task link
Issue
I notice quite a lot of feature requests on RCS that are marked as "In Development" and it is hard to find out who is developing it or where. Also it is hard to identify which feature requests are actually already done.
Usually a task link is included somewhere in the comments but this should be visible in a more obvious way.
In fact, the tag for "Mark as Duplicate" already handles this much better by requiring the hash for another duplicate feature request to be defined.
Add maniphest task when "In Development"
This is my proposal: It would be much easier to check if the feature is currently in development, if the link to a task is visible. Whenever a feature is in development there will be some Maniphest task related to it. This can be easily identified with a hash like "T12345". So whenever changing the status as "In Development", RCS should ask the author to add a maniphest task.
If that task is ever marked as resolved with a commit, it would be easy to mark the feature request as done as well. This could potentially even be automated.
4 Comments
On one hand yes, it will be a lot more convenient:
On other hand devs probbaly don't want extra "When it's ready? Why is this abandoned?" questions on dev tracker.
I think this is mostly really useful for those that have to moderate the feature requests here and keep them up-to-date. But thanks for the mockup! That's what I imagined too.
Also statistic counter and charts can be nice : )
Done! Brought this up to Francesco and for the time being we introduced the "Development URL" field, without the automatic check/state change.
There are several reasons for not having an automatic check between the post and the task/diff. For example the task can be closed/archived while the idea is still useful, a task can change purpose, the server load on checking constantly for a change in the task status, and also that Phabricator will soon be phased out for another system.
I've edited this post and added T1234 as an example. Francesco did the back-end and I added the button based on @fructdw's design (thanks!)