Allow postponing to a different milestone
Bug #509806 reported by
Martin Pitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
work-items-tracker |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Related to bug 509805, we should introduce a new syntax
description: POSTPONED to milestonename
with the following semantics:
* for the milestone which the WI is originally reported under, it counts as "postponed"
* for the "milestonename" milestone it counts as "todo"
for closing that WI there is currently no straightforward syntax. I propose that the WI gets copied to the new milestone section with status "done". The report engine already ensures that work items with identical descriptions are just counted once.
Related branches
lp:~jamiebennett/launchpad-work-items-tracker/add-later-support
On hold
for merging
into
lp:launchpad-work-items-tracker
- Martin Pitt (community): Needs Fixing
-
Diff: 204 lines (+30/-23)4 files modifiedcollect (+4/-1)
html-report (+11/-9)
report_tools.py (+4/-4)
wiki-status (+11/-9)
Changed in launchpad-work-items-tracker: | |
status: | New → Triaged |
importance: | Undecided → Medium |
importance: | Medium → Wishlist |
assignee: | nobody → Martin Pitt (pitti) |
Changed in launchpad-work-items-tracker: | |
status: | Triaged → In Progress |
summary: |
- Alllow postponing to a different milestone + Allow postponing to a different milestone |
Changed in launchpad-work-items-tracker: | |
status: | In Progress → Triaged |
Changed in launchpad-work-items-tracker: | |
assignee: | Martin Pitt (pitti) → nobody |
To post a comment you must log in.
+1 for me