target to series offers all of the pillar's series including obsolete ones
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
If you click on the link to target a bug to a series (aka add a bugtask for that release series), you end up taking to a page that has a list of *all* release series ever created for the project.
As an example:
https:/
Bazaar has 35 release series (we released 1/month for the last 3 years). At this point we are actually splitting things up a bit and having a real 2.0.x series versus the next 2.1 series. As such, there are really only 2 or 3 of the series that are considered 'active'.
It would be nice to have the page only show the active series, possibly with a fold-out to target arbitrary old series. If you compare the target page to:
https:/
It is fairly clear that Launchpad already understands that right now we only have 4 active series (1.18, 2.0, 2.1, 'trunk'), and the 1.18 series will probably be closed soon.
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Martin Pool (mbp) wrote | #1 |
| summary: |
- target to release gives a page of all series, without indication of + target to series gives a page of all series, without indication of 'active' |
| summary: |
- target to series gives a page of all series, without indication of - 'active' + target to series offers all of the pillar's series including obsolete + ones |
| tags: | added: bug-nomination bugs series |
Just a note that in most other contexts, disabled schedule objects are all-but-invisible. For instance you cannot target a bug to a disabled milestone unless you first reenable the milestone. So there is a kind of consistency argument, beyond just usability, for hiding the disabled ones.