Sort Milestones in Roadmap and NewTicket alphabetically (as an option)

[jan.linnenkohl@…]

I use Trac for different components with different version number. The milestones are sorted in the sequence I added them plus a sort over the date that is set.

It would be very nice to get them optional sorted alphabetically.

The milestone listbox in the "New Ticket" looks now as the following example:

• ComponentA 1.0
• ComponentB 2.1
• ComponentC 0.3
• ComponentC 0.4
• ComponentA 1.1
• ComponentB 2.3

I want to have an option in the "Roadmap" to sort it alphabetically and my be as default in the "New Ticket" settings. Then it should look like the following:

• ComponentA 1.0
• ComponentA 1.1
• ComponentB 2.1
• ComponentB 2.3
• ComponentC 0.3
• ComponentC 0.4

[anonymous]

The trunk already sorts the lists alphabetically and has done this for quite awhile. The roadmap still also sorts by due date, but that is a prefer feature.

[jan]

I think you are wrong for the NewTicket. I just looked at the ​https://ssl.bulix.org/projects/demo/newticket, where version 0.9b2 is running. There are the entries under milestones not sorted alphabetically. It seems to be sorted in the same order as in the roadmap. I would prefer the alphabetically order, because it's hard to find an special version in an unsorted listbox.

For the roadmap I would suggest another checkbox "Show milestones alphabetically" (in the same dialog as the checkbox "Show already completed milestones"). When I search for a special version it's hard to know, how the "due date" is set.

[Christopher Lenz]

Sorting by due date is the natural thing to do for milestones. Your problem is (AFAICT) that you're trying to maintain multiple projects in a single Trac environment. At least for me, milestones don't make sense on a per-component basis. After all, you want the entire system/project to reach a milestone, not just some part of it.

So, I don't think that we should officially support pseudo-multi-project deployment in Trac. Rather, we need #130 at some point, where stuff like this would be more natural.

[ma@…]

I support the request for the possibility to sort milestones alphabetically as an option… we use Trac for quite large projects with a number of milestones.. It can be hard to find the correct milestone for a ticket when you have to read a long list sorted by due dates (and closed milestones as well).

Marianne

[Christian Boos]

See also #1440.

[anonymous]

#13018 was closed as a duplicate.

This is still missing. We have many milestones in one Trac instance without a problem, except that the milestone sorting is confusing. Milestones already have names, so why not allow sorting by them as an option?

[tt2473@…]

I'm surprised to see that this request has been around for so long with no resolution. I too have many milestones in one TRAC instance and are unable to sort on the milestones. Why is sorting on the milestone such a problem to resolve?

[anonymous]

/path/to/tracenv/plugins/better_milestone_order.py:

from trac.util import embedded_numbers
from trac.ticket.model import Milestone

def better_milestone_order(m):
    return (not bool(m.completed),
            not bool(m.due),
            embedded_numbers(m.name))
old_select = Milestone.select
def new_select(cls, env, include_completed=True):
    milestones = old_select(env, include_completed)
    return sorted(milestones, key=better_milestone_order)
Milestone.select = classmethod(new_select)

[anonymous]

​th:wiki:RoadmapPlugin allows sorting milestones by name among other things.