ordering options should match data that is displayed in bug listings
Bug #295214 reported by
EmmaJane
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Abel Deuring |
Bug Description
In searching bugs related to.... on https:/
Match the options in the drop down search "sort by" to match the names of the columns on the page (e.g. Location vs. In). Include new column heads where none exist (e.g. Milestone).
Screen shot attached, of course.
Related branches
lp:~adeuring/launchpad/history-model
- j.c.sackett (community): Approve
-
Diff: 766 lines (+279/-104)9 files modifiedlib/lp/app/javascript/ordering/ordering.js (+32/-2)
lib/lp/app/javascript/ordering/tests/test_orderby_widget.js (+30/-0)
lib/lp/bugs/browser/bugtask.py (+5/-5)
lib/lp/bugs/browser/tests/test_bugtask.py (+21/-21)
lib/lp/bugs/javascript/buglisting_utils.js (+38/-5)
lib/lp/bugs/javascript/tests/test_buglisting_utils.html (+3/-0)
lib/lp/bugs/javascript/tests/test_buglisting_utils.js (+116/-58)
lib/lp/bugs/templates/buglisting.mustache (+10/-10)
lib/lp/bugs/templates/bugtask-macros-tableview.pt (+24/-3)
Changed in launchpad: | |
status: | New → Triaged |
Changed in malone: | |
importance: | Undecided → Low |
tags: | added: confusing-ui |
tags: | added: bug-columns |
Changed in launchpad: | |
importance: | Low → High |
summary: |
- match input and column headers searching bugs related to.... + ordering options should match data that is displayed in bug listings |
Changed in launchpad: | |
status: | Triaged → In Progress |
assignee: | nobody → Abel Deuring (adeuring) |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
When we did user testing a year ago, one thing we saw (though not with enough people yet to be a statistically reliable result) was that people didn't notice the sort menu at all. So one way of resolving this inconsistency would be to remove the menu completely, and use the column headers for sorting instead. That would solve this problem as well, but it would introduce two new problems: it would make choosing a sort order slower (because you'd need to wait for the initial results to load first), and there are some sort orders in the menu that don't have columns (so they'd need to have new columns or be dropped).