Sort by severity is incorrect

[bryan@…]

When I create any report and sort by the 'Severity' column, they sort in the following order:

• blocker
• critical
• enhancement ←- seems like this should be lower?
• major
• minor ←- should this be below 'normal'?
• normal
• trivial

They appear to be sorting in alpha order rather than severity order.

[bryan@…]

After further experimentation we found that the priority column also sorts alphabetically (rather than higher priority first as we'd expect).

So we worked around it by adding 1/highest, 2/high and so on, then removing the original values, via trac-admin priority commands. We did the same for severity (using 1/blocker, 2/critical, and so on - note we had to use slashes because trac-admin apparently doesn't like dashes in values!). This allows our reports to properly sort by priority or severity.

This did lead to an odd little annoyance which we don't mind but thought we'd tell you about anyway: the dropdown boxes don't seem to sort correctly! I'm attaching a jpeg image showing the mis-sorted dropdown boxes.

[bryan@…]

Screenshot of mal-sorted priority/severity dropdowns.

[Christopher Lenz]

How are you sorting by severity/priority? By clicking on the column headers, or by using an explicit ORDER BY in the report SQL?

[anonymous]

Ack… memory is hazy. I am sure the problem manifested when clicking column headers. I am pretty sure I tried ORDER BY queries (and had same issue) but I am not certain. I can't replicate the problem now, because I prepended digits to the priority/severity levels to force proper sorting even if the sort is alphanumeric.

[Matthew Good]

If you want to order your SQL query by priority you need to join on the "enum" table to get the numeric sortable order. This is done in the standard reports included with Trac, so you can use them as an example.