Unnecessarily difficult to find how to change status or reassign a bug
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Launchpad itself |
Medium
|
Matthew Paul Thomas | ||
Bug Description
Numerous reports, on IRC and in the duplicates of this bug, show that people have a lot of difficulty realizing how (or even whether) they can change the status or assignee of a bug.
From a letter from Mark:
* please put a small swizzle indicator on the left of every bugtask
row (left of the product/distro emblem) and make that a link to
drop open thebugtaskediting page
* add a small [edit] link to each row in a new column to the *right*
of the assignee, and make that ALSO drop down the task editing page
| Christian Reis (kiko) wrote : | #1 |
| Brad Bollenbach (bradb) wrote : | #2 |
I agree with your assessment. It's also consistent with what at least one user (tseng) reported in an impromptu user testing session. To paraphrase him, splitting one bug over two different pages "just doesn't compute."
| description: | updated |
| Matthew Paul Thomas (mpt) wrote : Re: Bug page doesn't give any hint as to how to assign or close a bug | #3 |
Closing a bug is bug 1320.
| Changed in malone: | |
| assignee: | nobody → bradb |
| status: | New → Accepted |
| description: | updated |
| Francis J. Lacoste (flacoste) wrote : | #4 |
How about just putting an explanation under the table: To change this bug status or assign it to someone, click on the product or distribution affected by the change ?
| Changed in malone: | |
| assignee: | bradb → nobody |
| Vincent Ladeuil (vila) wrote : | #5 |
Why not just add the pencil icon at the left of the name ? I think I may have give it try. (Yes, I also had to ask the question today: how can I change the status of a bug) and was kindly redirected here.
| Robey Pointer (robey) wrote : | #6 |
I ran into this too. No amount of playing around on the page helped, since I assumed that obviously for a project named "paramiko", a link called "paramiko" would go to the project page. I finally had to ask on IRC for help, assuming the page was just broken.
This bug looks like it has been open for a long time. :(
| Cheuksan Edward Wang (wang02139) wrote : | #7 |
Please increase the importance of this bug.
I'm hurt by this too. It'd be much more intuitive to use say, "Assigned To", to reassign bugs. Don't you agree?
Even though someone told me to use the 'bzr (upstream)' link, it still took me a long time to see it. I kept looking around the "Assigned To" area.
| Fabián Rodríguez (magicfab) wrote : | #8 |
I would propose adding two new links to the same form in the left hand menu just like "Visibility/
* "Assign to people/team" -> https:/
* "Assign/change status" -> https:/
| Matthew East (mdke) wrote : | #9 |
Seems to me like a pencil icon or expandable arrow icon on the left of the bug task would be fine for helping using figure things out. With 9 duplicates, it's certainly worth increasing the severity of this bug to High, IMO.
| Tom Haddon (mthaddon) wrote : | #10 |
I think any of the recommendations as to how to fix this proposed above would be fine. Personally I found myself looking for it in the "Actions" pane on the left, so my vote would be to put it there. I also agree it should be a higher priority, as I'm sure there are numerous bugs out there that are sitting in a status that's not entirely accurate because people don't know how to edit that value.
| description: | updated |
| Changed in malone: | |
| assignee: | nobody → bjornt |
| status: | Confirmed → In Progress |
| Björn Tillenius (bjornt) wrote : | #11 |
I have submitted a patch to PQM that adds a swizzle indicator, but mpt doesn't agree with Mark on making the target name link to the target itself and adding an [edit] link for each row, so I'll let him handle the rest.
| Changed in malone: | |
| assignee: | bjornt → mpt |
| status: | In Progress → Confirmed |
| Christian Reis (kiko) wrote : | #12 |
I believe this is now properly addressed. If this is still an issue we can revisit this work in another bug with more concrete user data if possible.
| Changed in malone: | |
| status: | Confirmed → Fix Released |
| Matthew Paul Thomas (mpt) wrote : | #13 |
(The sequel to this bug report is bug 137448.)
I agree with the problem description (though I couldn't find a reference to it in bug 1056). I don't have a clue off-hand as to how to solve this without doing away with the bug page and going with the "always-