On Nov 20, 2007 4:00 PM, Matthew Paul Thomas <email address hidden> wrote:
> I don't understand what it would mean to have a "No, undo" button
> alongside a "Yes, continue" button. Either the reassignment has
> happened, in which case "continue" would be a no-op, or it hasn't
> happened, in which case "undo" would be incorrect.
>
> All that would be necessary for an "Undo" button would be a <form> with
> a hidden assignee field representing the previous assignee, so clicking
> the button would reassign back to him/her.
"Continue" would just be a way to navigate away from the notification.
I suppose it could just be a box displayed on top of the bug page, in
which case you're right, just an "undo" would be enough.
I still see some nuisance caused by the wrong assignee getting mail,
by them potentially being shown a private bug, and so on. But I can
see the downside of confirmation boxes too.
On Nov 20, 2007 4:00 PM, Matthew Paul Thomas <email address hidden> wrote:
> I don't understand what it would mean to have a "No, undo" button
> alongside a "Yes, continue" button. Either the reassignment has
> happened, in which case "continue" would be a no-op, or it hasn't
> happened, in which case "undo" would be incorrect.
>
> All that would be necessary for an "Undo" button would be a <form> with
> a hidden assignee field representing the previous assignee, so clicking
> the button would reassign back to him/her.
"Continue" would just be a way to navigate away from the notification.
I suppose it could just be a box displayed on top of the bug page, in
which case you're right, just an "undo" would be enough.
I still see some nuisance caused by the wrong assignee getting mail,
by them potentially being shown a private bug, and so on. But I can
see the downside of confirmation boxes too.
--
Martin