This is a result of the client-side js sort, which is a bmo local hack
Assignee: query-and-buglist → nobody
Component: Query/Bug List → Bugzilla: Other b.m.o Issues
Product: Bugzilla → mozilla.org
QA Contact: default-qa → other-bmo-issues
Version: unspecified → other
I think the client-side sorting needs to make an ajax call to get the sort keys (this probably affects other columns besides severity, too, like priority and milestones, for example). That or we need to find some way to expose the sort keys in the html so the JS can act on it.
If that's feasible, just publishing a JS array in the page that maps the severity abbreviations to numbers (then sorting by this number) would probably do.
some japanese developers claims this, too. :-) # so, watching. Another way, how about adding new sort handler like sort_severity and set class sorttable_severity?
This is probably true for all the fields that have sortkeys, including status, resolution, priority, severity, op_sys, platform, and version.
Summary: Sorting by severity sorts alphabetically → Sorting by severity, priority, milestone, etc. sorts alphabetically
Okay, there's a fix for this in the Everything Solved repo: Committing to: /var/www/html/everythingsolved.com/bzr/mozilla/3.0/ modified buglist.cgi modified Bugzilla/Field.pm modified template/en/default/list/table.html.tmpl Committed revision 5169.
Assignee: nobody → justdave
revno: 5186 committer: David Miller <firstname.lastname@example.org> branch nick: bugzilla-test timestamp: Mon 2008-05-19 22:19:25 -0700 message: Import current changes from Everything Solved This won't be live on bmo until bug 434921 is marked resolved.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.