Mass migration of bugs from one milestone to another
Bug #617303 reported by
Mikkel Kamstrup Erlandsen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Pretty much all of the LP projects I participate in (both professionally and spare time) we don't complete all the bugs assigned to some given milestone, but instead close the milestone and migrate all the remaining bugs by hand. This can be quite tedious for medium- to large projects. It would be nice to have some sort of mass migration option "Assign all open bugs to milestone X".
The equivalent for bug statuses is bug 41702, and for tags bug 76083.
Same could be done for blueprints, but that is prolly another bug...
| summary: |
- Mass mrigration of bugs from one milestone to another + Mass migration of bugs from one milestone to another |
| description: | updated |
Revision history for this message
| Deryck Hodge (deryck) wrote | #1 |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: feature |
| Changed in launchpad-registry: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: milestone |
Revision history for this message
| Bryce Harrington (bryce) wrote | #2 |
| tags: |
added: milestones removed: milestone |
To post a comment you must log in.
This is a low priority for the bugs team, but I'm sure "mass-editing" bugs will get more attention some day. I'll also add a registry task since they look after the milestone code primarily. I'm not sure how this would fit in their priorities.