Modify ↓
Ticket #9141 (new defect)
Opened 2 years ago
Last modified 17 months ago
'Retarget associated tickets' does not respect [milestone-groups] config
| Reported by: | jakob.gruber@… | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-0.1X |
| Component: | roadmap | Version: | 0.11.6 |
| Severity: | normal | Keywords: | milestone-groups milestone |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
Hi,
first of all thanks for a great application.
We recently completed a large milestone with 300 associated tickets. We use a custom [milestone-groups] section to accomodate QA after the ticket has been marked closed by the developer.
[milestone-groups] active = * active.css_class = open active.label = in progress active.order = 1 closed = closed,verified closed.order = 0 closed.overall_completion = true closed.query_args = group=resolution
After closing the milestone, all tickets with verified status were moved to the next milestone, leaving us with ~20 tickets on the completed one.
'Retarget associated tickets' should respect the [milestone-groups] section.
Attachments
Change History
comment:1 Changed 17 months ago by cboos
- Milestone set to next-major-0.1X
comment:2 Changed 17 months ago by rblank
Sounds reasonable indeed.
Note: See
TracTickets for help on using
tickets.



Sounds a reasonable expectation. What do others think?