Redmine

As if the sorting is made on some internal key?

AFAIK versions are sorted by due date first, and names after that. Still no bug that I can see.

In the screenshot, the groups are not sorted like expected (from a user point of view I mean, this may be a "standard" SQL behavior, I'm not sure). Group 1.1.0 is displayed before group 1.0.1, whereas Michalis asked for a sort by target version ascending.

Ah, I think I know what's happening :-)

The "group by" and "sort by" don't influence each other. If you remove the "group by", the issues will be sorted correctly/as expected, if you specify a "group by", the issues inside the groups will be sorted correctly/as expected, but that won't influence the order of the groups. In the case where you select the same attribute to "group by" and "sort by", well, they are sorted "correctly" inside each group, though you don't see anything of it as they all have the same value for that attribute, rendering any sort of sorting moot.

Do you think we should / could find a workaround ?

OH: I just discovered you can "GROUP BY blah ASC" in at least sqlite and mysql. Needs to be tested, but we may have a clean workaround if it's supported on each of our databases and/or by rails adapters.

Jean-Baptiste Barth wrote:

OH: I just discovered you can "GROUP BY blah ASC" in at least sqlite and mysql. Needs to be tested, but we may have a clean workaround if it's supported on each of our databases and/or by rails adapters.

It'd be very intuitive to have it grouped, and even choose which way to group in another dropdown (just like the ordering in the other drop downs)