Option to specify status list which will be retargeted when closing milestone

[arkinform <arkinform@…>]

By default, only status "closed" retargeted.

[Remy Blank]

On the contrary: all tickets whose status is not closed are re-targeted. Which makes sense: tickets that have been closed against a milestone should remain closed against that milestone.

So the question is: should we allow configuring the statuses for which tickets will not be re-targeted when closing a milestone. I always have a negative a priori against rarely used configuration options, but I'm open to discussion.

[arkinform]

We have short week milestones for development planning inside one long milestone. And we have status like "returned to revision (rework)". It means that the tester found the small bug in implementation of this feature. We fix such bugs within the same ticket. We close week milestone on completion of the week. And at this moment the milestone may contain "returned to revision" ticket. But we don't want to retarget "returned to revision" tickets because developer implemented the main volume of work within this milestone.

[Christian Boos]

One way to do this would be to make a patch adding an extension point for the method selecting the tickets to retarget and then implement a plugin for that extension point.

Another way would be to have a configurable query expression for selecting the tickets. Even if we don't have yet a very powerful query language for the tickets, that could be enough to address your current need (something like status!=closed&status!=rework).

PatchWelcome!