Originally reported on upstream: https://secure.phabricator.com/T12144 - which was closed as "Won't fix"
I use milestones to track versions of an app I'm developing. Multiple times, I've needed to add milestones to represent new versions of the app (for example, I've created a 1.0 milestone to track release tasks but I've needed to create a 0.5 version to handle more pressing private beta bugs). The current workflow is:
- Choose "Create Next Milestone"
- Connect to my database, SELECT id, name, milestoneNumber FROM phorge_project.project WHERE parentProjectPHID="PHID-PROJ-XXX" AND milestoneNumber > 0;
- Edit the milestoneNumber field for the milestone and all milestones after it to implausibly high numbers. (This step is required because of primary key checks)
- Edit the milestoneNumber field to represent my desired ordering.
This could be easily automated. There is a concern about other parts of the UI being broken by this change, so we should do some testing before pushing to stable.