The consequences of choose an item in a picker is not obvious
Bug #800361 reported by
Curtis Hovey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
Curtis Hovey |
Bug Description
New users to Lp report that they were surprised that choosing a item such as a user would close the picker and assign the user. When assigning a user to a bug, the user sees a link to assign himself. The action is explicit, it sets the expectation that the rest of the picker is explicit. The users imagined that choosing a user in the list would reveal more information about the user and a link to assign the user.
Changed in launchpad: | |
assignee: | nobody → Ian Booth (wallyworld) |
Changed in launchpad: | |
assignee: | Ian Booth (wallyworld) → j.c.sackett (jcsackett) |
Changed in launchpad: | |
status: | Fix Committed → In Progress |
tags: | removed: qa-needstesting |
Changed in launchpad: | |
status: | In Progress → Triaged |
tags: | added: bad-commit-13605 qa-bad |
tags: |
added: qa-ok removed: qa-bad |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think this would be a really good thing to specify in the ui style
guide, so it can at least trend towards being consistent everywhere.
At the moment it is not: consider the assignee picker vs the filebug
suggestions vs retarget to vs ...
Something like "when we should a list of objects from which the user
is going to pick on (eg as a bug target project or a bug assignee
person), we should show them as radiobuttons with a separate submit
button" or "... we show them as list items where clicking one item
immediately selects it" or whatever.