Milestone status sorting puts invalid bugs first

[Martin Pool]

On this page https://edge.launchpad.net/bzr/+milestone/1.0alpha1

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)

[Christian Reis (kiko)]

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?

[Martin Pool (mbp)]

On Dec 4, 2007 6:46 AM, Christian Reis <email address hidden> wrote:
> 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?

I agree it's only a mild problem and not a priority. Normally there
are so few invalid bugs it doesn't matter, and if there were I could
untarget them; or do an advanced search for only open bugs on this
milestone.

But clicking twice does not give me what I want:

  ascending order is: invalid, active, fixed
  descending order is: fixed, active, invalid

--
Martin

[Matthew Paul Thomas (mpt)]

Reproduced on <https://launchpad.net/launchpad/+milestone/1.1.12>, where clicking on Status gives New, Wontfix, Confirmed, Triaged, In Progress, Fix Committed, Fix Released. The position of Wontfix is wrong.