Modify ↓
Opened 15 years ago
Last modified 9 years ago
#9141 new defect
'Retarget associated tickets' does not respect [milestone-groups] config
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | next-major-releases |
Component: | roadmap | Version: | 0.11.6 |
Severity: | normal | Keywords: | milestone-groups milestone bitesized |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal 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 (0)
Change History (3)
comment:1 by , 14 years ago
Milestone: | → next-major-0.1X |
---|
comment:3 by , 9 years ago
Keywords: | bitesized added |
---|
Note:
See TracTickets
for help on using tickets.
Sounds a reasonable expectation. What do others think?