User affiliation with context in person picker is unclear
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
When you choose a person with the person picker, it's unclear what the affiliation the returned person has with the project.
Some comments from the exploratory testing:
* When I try to assign a bug in Launchpad and search for "huw" I notice there is a little LP icon next to my name but no explanation of what it means. I'm guessing it means I'm a member of the team that owns the project of the bug I'm assigning someone to. If so it might be better to indicate that in a more obvious way (quite possibly with text) as it would seem quite important.
* when I search for matsubara on the oops-tools project to assign driver, there's no UI saying matsubara is related to the project (I'm the owner). Must #2 from the LEP says the context should show the affiliation
Related branches
- Curtis Hovey (community): Approve (code)
-
Diff: 219 lines (+117/-19)3 files modifiedlib/lp/registry/model/pillaraffiliation.py (+24/-2)
lib/lp/registry/tests/test_pillaraffiliation.py (+83/-12)
lib/lp/testing/factory.py (+10/-5)
- Curtis Hovey (community): Approve (code)
-
Diff: 886 lines (+622/-57)7 files modifiedlib/lp/app/browser/tests/test_vocabulary.py (+16/-7)
lib/lp/app/browser/vocabulary.py (+9/-3)
lib/lp/registry/configure.zcml (+28/-3)
lib/lp/registry/model/pillaraffiliation.py (+110/-21)
lib/lp/registry/tests/test_pillaraffiliation.py (+437/-15)
lib/lp/services/features/flags.py (+4/-0)
lib/lp/testing/factory.py (+18/-8)
| summary: |
- User affilition with context in person picker is unclear + User affiliation with context in person picker is unclear |
| tags: | added: person-picker |
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in launchpad: | |
| assignee: | nobody → j.c.sackett (jcsackett) |
| Changed in launchpad: | |
| status: | Triaged → In Progress |
| j.c.sackett (jcsackett) wrote | #2 |
| Changed in launchpad: | |
| assignee: | j.c.sackett (jcsackett) → nobody |
| status: | In Progress → Triaged |
| Curtis Hovey (sinzui) wrote | #3 |
| Changed in launchpad: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| Ian Booth (wallyworld) wrote | #4 |
| Changed in launchpad: | |
| status: | Triaged → In Progress |
| Launchpad QA Bot (lpqabot) wrote | #5 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
Clear user affiliation (UI Test)
Project affiliation is not clearly conveyed to the beta testers viewing the person picker.
• The project icon does not clearly state that the user is affiliated with the project, thus is more likely to be the user to choose.
• The icon does not state how the user is affiliated, which confirms the reason to choose.
I happen to know that the first effort to show implementation only the project icon when the user is the project maintainer, Yet I am surprised sometimes when I see, or do not see, the icon.
I need to know if the user is a maintainer, driver, bug supervisor, or security contact for the project. The project icon can be helpful, but not every project has an custom icon. The user's role in a project is important. I am more like to to assign a bug or blueprint to a driver than a maintainer or a bug supervisor. Know that the user is in many roles might be helpful.
In the special case of a bug, I may want to know if the user is affiliated with one or more the affected projects. I am more likely to assign a bug to a user affiliated with both the upstream project and Ubuntu than to another user.
I believe a successful presentation of affiliation would also work with comments. I want to know who speaks for a project. When I can which users are drivers or bug supervisors in the comments of a bug, I will have better knowledge about the importance of what is written.