Marking milestones as active is a tedious method of picking appropriate milestones to use
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Undecided
|
Unassigned | ||
Bug Description
When a project has a lot of milestones (e.g. LightDM) it takes a lot of time to manage them by marking old milestones as inactive to stop them polluting the milestone list when editing bugs. This is particularly bad since the list is hard to use since it doesn't seem to have a logical order (bug1512213) and shows all milestones even if a task it for a particular series (bug 1512216). Occasionally I need to retroactively target a bug to a milestone I have marked as inactive, and this requires a tedious mark as active - update bug - mark as inactive sequence to get around this.
It seems like Launchpad could be smarter about this, as the milestones I spend the majority of time when editing bugs are the unreleased milestones from active series. The graph on the project page marks these with white circles, so there is an existing case where these are recognised as special.
There's probably a number of solutions to this but improvements I can think of are:
- Showing these active unreleased milestones with a "show all milestones" button to show everything
- Showing the graph so they are easy to find in context
Ideally the "active" concept could be removed entirely as this is a project management step that seems unnecessary.
