confirmation before assigning bugs to unlikely people

Bug #138504 reported by Martin Pool
2
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

Revision history for this message
Martin Pool (mbp) wrote :

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

Cheers

Revision history for this message
Martin Pool (mbp) wrote : Re: confirmation before assigning bugs

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.