Milestones should be ordered by debversion, then chronologically when changing bug status

[Jamu Kakar]

When a project uses milestones, and you have permission to change the milestone for a bug in that project, the "Milestone" menu lists the milestones alphabetically. It should list them chronologically by due date. It might even be nice to include the milestone due date in the listing, as in, "Name (YYYY-MM-DD)".

[Martin Pool (mbp)]

Dupe of 38721?

[Matthew Paul Thomas (mpt)]

Maybe, but I'm confused by the "when editing bug details" bit. I don't see any list of milestones when editing a bug's description. Jamu, can you give us an example URL?

[Jamu Kakar (jkakar)]

This is a private bug, but you (mpt) ought to have access to it:
https://bugs.beta.launchpad.net/landscape/+bug/72569

I can't find a public bug that I have enough priviledges for to edit
it's milestone; therefore, I can't find a public bug that displays a
Milestone menu. Anyway, If you click on the '... (upstream)' link in
the table at the top of the page (in the Affects column) the page
unhides the section of controls that allows you to edit Product, Status,
Importance and Milestone. The issue this bug is about is similar to
38721 but is specifically about the milestone menu in this context.

Does this help clarify the issue?

[Matthew Paul Thomas (mpt)]

Ah, I see it now.

[Curtis Hovey (sinzui)]

Milestone cannot be sorted by their expected date because not every milestone has one. To show milestones sorted for a series, er use lp.registry.model.milestone.milestone_sort_key, which does several hacks to make the list appear correct.

[Robert Collins (lifeless)]

In the current model the milestones for a bugtask from the product/series - and that has a unique constraint across the product. As such, for any given task there is already a unique sort on the name.