Comment 2 for bug 138504

https://bugs.edge.launchpad.net/launchpad/+bug/138504

> All other things being equal, any solution that doesn't involve a
> confirmation alert is better. (Though it's usually harder to
> implement!)

I agree in general; however in this case I feel fairly sure the
confirmation will only occur when the user really has made an error so
it's not so bad.

> 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>.

That would be nice too.

> 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?)

I think that would also work, but in this particular case confirmation
might be better. It's not obvious to users that the notification mail
can be forestalled in this way, and even temporarily assigning it to
the wrong person feels like I've made a mistake.

--
Martin