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
autocomplete menus for person fields, the suggestions could be ordered
by karma within the project, rather than just by global karma. Added to
<https://launchpad.canonical.com/SuggestionSearchControl>.
For fixing the problem when it does occur, Launchpad could warn you on
the resulting page but *not* require you to confirm it. Then if it's
not what you meant, you can fix it. <http://launchpad.net/bugs/138500>
(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?)
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