Sorting by severity, priority, milestone, etc. sorts alphabetically

RESOLVED FIXED

Status

()

bugzilla.mozilla.org
General
--
minor
RESOLVED FIXED
10 years ago
7 years ago

People

(Reporter: wenzel, Assigned: justdave)

Tracking

({regression})

Details

(Reporter)

Description

10 years ago
When you sort a buglist by severity with the new Javascript sort function, the list will turn out to be sorted alphabetically by the names of the severities rather than their meaning: blocker > critical > enhancement >... > minor > normal.

It would make more sense to sort the list by actual severity, meaning: normal > minor > enhancement.

That is, I believe, how the sorting worked before the instant Javascript sorting was introduced (and still works if you disable JS).
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
Blocks: 425607
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.
Keywords: regression
(Reporter)

Comment 3

10 years ago
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.

Comment 4

10 years ago
some japanese developers claims this, too. :-)
# so, watching.

Another way, how about adding new sort handler like sort_severity and set class sorttable_severity?

Comment 5

10 years ago
  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

Comment 6

10 years ago
  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

Updated

10 years ago
Status: NEW → ASSIGNED
revno: 5186
committer: David Miller <justdave@mozilla.com>
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

Updated

10 years ago
Blocks: 441832
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.