confirmation before assigning bugs to unlikely people
Bug #138504 reported by
Martin Pool
This bug report is a duplicate of:
Bug #138500: Warn if assigning a bug to someone not involved with the project.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
New
|
Undecided
|
Unassigned |
Bug Description
Once or twice I have made a mistake when assigning a bug, because, for
example, robert is lifeless on launchpad, not robertc (who is someone
else.)
Maybe when assigning a bug there could be a confirmation dialog like this:
robertc (Robert Chatwick) has no other assigned or subscribed bugs
for $product, and is not a member of the product team. Are you sure
you want to assign a bug to them? y/n
To post a comment you must log in.
mpt says:
All other things being equal, any solution that doesn't involve a
confirmation alert is better. (Though it's usually harder to
implement!)
For preventing this problem in the first place, when we have /launchpad. canonical. com/SuggestionS earchControl>.
autocomplete menus for person fields, the suggestions could be ordered
by karma within the project, rather than just by global karma. Added to
<https:/
For fixing the problem when it does occur, Launchpad could warn you on launchpad. net/bugs/ 138500>
the resulting page but *not* require you to confirm it. Then if it's
not what you meant, you can fix it. <http://
(I think this is how new bug tags should work, too.) And if you fix it
within five minutes, before the mail notification goes out, the
mistaken assignee should receive zero notifications. (Where can I find
instructions on testing this locally?)
Cheers