Enhancement: bugresolve should optionally set the milestone

Bug #1292184 reported by David Britton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tarmac
Fix Released
Medium
David Britton

Bug Description

Some launchpad workflows don't pre-set the milestone, instead collecting all fixes on a series. For this workflow, it would be helpful if tarmac would fill in the "correct" milestone, using something like the following logic:

1) nearest milestone with target date in the future
2) if no milestones are in the future, sort remaining open milestones lexically by name and pick the first
3) If all milestones have dates and we are past all dates, pick the newest of those.
4) override all that logic with a config setting of "default_milestone" which is the specific milestone name to use (which will even select a non-active milestone).

Related branches

David Britton (dpb)
Changed in tarmac:
assignee: nobody → David Britton (davidpbritton)
dobey (dobey)
Changed in tarmac:
status: New → In Progress
importance: Undecided → Medium
dobey (dobey)
Changed in tarmac:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.