Re-assigning bug reports to another package is a frustrating process
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Undecided
|
Unassigned | ||
Bug Description
Sometimes users report bugs against the wrong package. If this happens, someone will reassign the bug report to the correct package. However, in many cases it seems, a second task then gets added back to the bug report after it was reassigned, against the package that the reporter initially reported the problem against. This is because the reporter clicks an old link (maybe from an e-mail) or someone finds the report from an old link in a forum, and is presented with a screen similar to the screenshot I've attached, and they seem to feel compelled to press the "Yes, report it in 'package x'" button nearly every time.
This then adds the original (and incorrect) task back to the bug report, after someone already re-assigned it, thus re-subscribing everybody who isn't interested in it. Someone then has to come along and mark the task invalid again. In most cases, I also remove the source package name from the invalid task (leaving the invalid task just against 'Ubuntu'), so it unsubscribes those people who were automatically subscribed but might not be interested.
Unfortunately, in some cases, the original task then gets added again by someone else, and it becomes impossible to remove on the third time (I can only mark it invalid, which still leaves people subscribed).
This creates extra work, and creates extra bug spam for people who are inadvertently subscribed to bug reports that they might not be interested in.
Perhaps the "Yes, report it in 'package x'" button could be made less "in-your-face" so that people aren't tempted to press it every time they see it (maybe put it at the bottom of the page)?
Note, the bug report in the screenshot was originally opened against fast-user-
Some other examples of where this has happened:
https:/
https:/
| Chris Coulson (chrisccoulson) wrote | #1 |
