Opened 9 years ago

Last modified 9 years ago

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.

Changed 9 years ago by ja11sop@…

  • description modified (diff)
  • summary changed from ProjectAdmin can specify and ordering for Milestones to ProjectAdmin can specify an ordering for Milestones

Changed 9 years ago by ja11sop@…

  • description modified (diff)

Changed 9 years ago by ja11sop@…

  • owner set to ja11sop@…

Changed 9 years ago by ja11sop@…

  • status changed from new to assigned

Changed 9 years ago by ja11sop@…

  • status changed from assigned to closed
  • resolution set to fixed
  • description modified (diff)

Changed 9 years ago by ja11sop@…

  • component changed from agiletrac patch to core to release planning

Changed 9 years ago by jamiea

  • status changed from closed to reopened
  • resolution fixed deleted

Changed 9 years ago by jamiea

  • status changed from reopened to sized
  • test_complete_size set to 5
  • doc_complete_size set to 0
  • acceptance_complete_size set to 3

Changed 9 years ago by jamiea

  • acceptance_complete_date set to 07/19/08
  • status changed from sized to closed
  • resolution set to DONE
  • test_complete_date set to 07/19/08
Note: See TracTickets for help on using tickets.