Prevent assignee changes on fixed bugs
Bug #632288 reported by
era
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I subscribe to a moderately large number of bugs. While the amount of assignee spam is not significant, it happened twice in a week that somebody apparently by mistake assigned an already-fixed bug to themselves. In general, I would say this happens about twice per three months for me.
I'm not sure requiring karma is a good barrier to this sort of mistake, but it would seem like a suitable deterrent for cases where newbies don't know what button to click on. I would imagine it very rare for somebody to know how to assign bugs before they have made a single comment to any bug (although I guess it could happen, if a veteran creates a new Launchpad account, for example).
Revision history for this message
| Deryck Hodge (deryck) wrote | #1 |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: bug-page feature |
| summary: |
- Require karma for fiddling with assignee etc + Prevent assignee changes on fixed bugs |
To post a comment you must log in.
I don't think we should prevent users from assigning themselves if they lack karma. Working on a bug is a nice way to get karma. ;) However, I understand the problem and know that it can be frustrating when dealing with a large number of bugs.
I would prefer favoring the "lock changes to fixed bugs" option, but I cannot find an existing bug for this. I'm sure there was one, though. Bug #73122 is a general "lock bugs" bug. Anyway, I'll keep this one around to track the request for assignee.
Thanks for the bug report!
Cheers,
deryck