Default ordering in bug listings is typically unhelpful
Bug #903359 reported by
Aaron Bentley
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Abel Deuring |
Bug Description
When you change the ordering in dynamic bug listings, it always defaults to ascending order. But descending order is usually more useful, or equally useful.
- When I order by importance, I usually want to see the most important
- When I order by heat, I usually want to see the hottest
- When I order by date, I usually want to see the most recent
- When I order by number, I usually want to see the highest
The only cases where ascending order is clearly a better default is when sorting text, and for me at least, that's a rare case.
Related branches
lp:~adeuring/launchpad/bug-903359
- Deryck Hodge (community): Approve
-
Diff: 309 lines (+112/-65)5 files modifiedlib/lp/app/javascript/ordering/ordering.js (+33/-28)
lib/lp/app/javascript/ordering/tests/test_orderby_widget.js (+43/-15)
lib/lp/bugs/browser/bugtask.py (+21/-21)
lib/lp/bugs/browser/tests/test_bugtask.py (+15/-0)
lib/lp/bugs/javascript/buglisting_utils.js (+0/-1)
Changed in launchpad: | |
assignee: | nobody → Abel Deuring (adeuring) |
status: | Triaged → In Progress |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Different people will have different expectations here; I usually want to see smaller numbers when I use bug number, for example. But I generally agree with your assessment here. I think descending is better as the first shown, if we can't configure each button to have it's own initial sorting. And now that I type that, I think that may be confusing. So descending it is!
But we should recognize that any initial order will inevitably seem odd to someone, depending on which order by button he/she clicks.