Edgewall Software

Opened 11 years ago

Last modified 5 years ago

#9141 new defect

'Retarget associated tickets' does not respect [milestone-groups] config

Reported by: jakob.gruber@… 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:



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.

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 Christian Boos, 10 years ago

Milestone: next-major-0.1X

Sounds a reasonable expectation. What do others think?

comment:2 by Remy Blank, 10 years ago

Sounds reasonable indeed.

comment:3 by Ryan J Ollos, 5 years ago

Keywords: bitesized added

Modify Ticket

Change Properties
Set your email in Preferences
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.