Milestone status sorting puts invalid bugs first
Bug #172952 reported by
Martin Pool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
On this page https:/
when sorted by status, Invalid bugs come first. I think this is wrong; bugs that have been definitively closed as invalid or wontfix are less important than bugs that are still open or in progress.
(follows on from bug 62495, but different)
It's really not very easy to fix this (i.e. we'd need to change the status ID and then update the bugtask status accordingly, in one go) and I see this as being a really mild inconvenience if you can click twice on the header and get the sort order you want. Are you sure this is worth investing time into?