userstory #8 (closed: DONE)
ProjectAdmin? can specify an ordering for Milestones
| Test Complete Size: | 5 | Test Complete Date: | 07/19/2008 |
|---|---|---|---|
| Documentation Complete Size: | 0 | Documentation Complete Date: | |
| Acceptance Complete Size: | 3 | Acceptance Complete Date: | 07/19/2008 |
| Reported by: | ja11sop@… | Owned by: | ja11sop@… |
| Milestone: | Patch Against Trac 0.11 | Component: | release planning |
| Version: | Keywords: | ||
| Cc: | Blocked By: | ||
| Blocking: | Patch SVN Revision: | ||
| Patch Trac Version: | |||
| In Iterations: | 7 |
Description (last modified by ja11sop@…) (diff)
ProjectAdmin? can specify an ordering for Milestones
Basically this would involve saying one milestone depended on another.
It probably makes sense for this to be a "happens after" relationship. This would mean that older milestones would not need to be updated to reflect the presence of newer milestones. It would also mean that a default value of the latest milestone should be provided as the default value when creating a new milestone.
Well actually that turned out to not be a doable solution. Instead we've opted for a priority value for each milestone. Milestones can have the same priority as others in which case due dates and naming take precedence. Priorities are not displayed directly. Rather the user can chose to set the priority higher, lower or the same as another milestone.
Change History
Have a look at the list of modified files related to this ticket.
