Bugzilla does a string sort instead of a numerical sort on the milestones when you click to sort it by milestones. For instance, if you have bugs for M10, M15, M7, M1, and M8 the will be ordered as M1,M10,M15,M7,M8 instead of M1,M7,M8,M10,M15.

This is a problem because a milestone could be anything from a string (with specially defined sort order), number or date. Could Bugzilla somehow be changed to do numeric sort order if all the Milestones are numeric text?

tara@tequilarista.org is the new owner of Bugzilla and Bonsai. (For details, see my posting in netscape.public.mozilla.webtools, news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)

all yours don

This is an old bug. It's fixed. The new milestone method where it lets you define custom milestones for each product lets you define the sort order however you want within each product (each milestone gets a sort key, which you only see when you edit the milestone list, and the users never see it, it just affects what order they sort in).

Well, almost. It doesn't use that sort key when displaying a list of bugs, sorted by milestone.

It does for me. I just tried setting up a dummy product and entered a bunch of bugs in it. I left the --- milestone, and set up new ones as follows: name sortkey Z 10 A 50 Deferred 1000 If it behaves as you suggest, when viewing a buglist, those should sort with A at the top, and Z at the bottom, with Deferred between them, but I got Z at the top, Deferred at the bottom, and A in the middle, just like the sort keys suggest. Although now that I think about it, it's also the order they were entered in. Does the situation in question involve sort keys that are not in order in the database? (I'll try it on the same test data and report back)

OK, I changed the sort key to 100 on 'Z' in that list above (leaving it in its position within the list), and it correctly changed its position in the bug list when sorted by milestone. Looks like it works to me.

So what's the verdict, now? This still looks to me like it's fixed.

i believe it to be fixed too. closed.

In search of accurate queries.... (sorry for the spam)

verif.

Moving closed bugs to Bugzilla product