Terminology: "least recently changed" confusing
Bug #676825 reported by
Yuv
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Jonathan Riddell |
Bug Description
IN the process of evaluating Launchpad as a bug tracker for our Open Source project, I collected feedback from our varied, international community.
A non-native speaker reported "least recently changed" as sorting order in the bug tracker to be confusing. As non-native speaker myself I can confirm.
Suggestion: "last changed" instead of "most recently changed" and "first changed" instead of "least recently changed". May not be elegant, but more people understand last/first than least/most.
Related branches
lp:~jr/launchpad/676825-most-neglected
- j.c.sackett (community): Approve
- Matthew Revell (community): Approve (text)
-
Diff: 72 lines (+7/-7)4 files modifiedlib/lp/bugs/stories/bugtask-searches/xx-sort-orders.txt (+2/-2)
lib/lp/bugs/templates/bugtarget-macros-search.pt (+1/-1)
lib/lp/code/browser/branchlisting.py (+1/-1)
lib/lp/code/stories/branches/xx-branch-listings.txt (+3/-3)
lp:~mbp/launchpad/676825-not-recently-changed
- Curtis Hovey (community): Approve (code)
-
Diff: 39 lines (+6/-6)2 files modifiedlib/lp/bugs/stories/bugtask-searches/xx-sort-orders.txt (+2/-2)
lib/lp/bugs/templates/bugtarget-macros-search.pt (+4/-4)
Changed in launchpad: | |
assignee: | nobody → Jonathan Riddell (jr) |
tags: | added: dublin |
tags: |
added: qa-ok removed: qa-needstesting |
tags: | added: text |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This fix for this is easy -- i.e. changing the terms in the form. The hard part is getting agreement on what terms are better.