Ticket #6594 (closed enhancement: duplicate)
Opened 4 years ago
Last modified 4 years ago
When adding Milestones, they should also, optionally, be added as tickets.
| Reported by: | anonymous | Owned by: | cmlenz |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | roadmap | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
Sometimes it would be convenient if milestones could have other milestones as dependencies.
Ex.
Milestone: Release 1.0
Might have Milestones:
Add Major Feature X
Update Documentation to reflect version changes
Beta Test 1.0
Move to New DB
in addition to any other Enhancement/Bug? tickets
The easiest way I see to implement this is to have milestones be added as tickets, with a severity of "milestone". The ticket can then, optionally, be assigned a milestone.
So in the above example, I would create Milestone "Beta Test 1.0". A new ticket with severity "milestone" would be created. I could then assign the ticket to the "Release 1.0" milestone.
When calculating the progress of a milestone, you would include the progress of any sub-milestones.
When you marked a milestone as complete, the corresponding ticket would be closed; if you closed the ticket, the milestone would be marked as complete.
Attachments
Change History
comment:1 Changed 4 years ago by eblot
- Resolution set to duplicate
- Status changed from new to closed
Duplicate of #3003