180296 - The requestee gets no email notification about canceled requests addressed to him

Status: NEW

(Bugzilla :: Email Notifications, enhancement)

Description

[[e-mail]]

I cancelled a review, and got notified, instead of the reviewer:

 <[e-mail]> has cancelled your request for review on bug #163425
(Some tree headers should not have sort feedback), attachment #100035 [details] [diff] [review] (Better
patch).

http://bugzilla.mozilla.org/attachment.cgi?id=100035&action=edit

P.S. Will all my review requests go out with a leading space?

Comment 1

[Malcolm Rowe]

(I guess the leading space separates your real name [blank, in your case], from 
your email address)

Comment 2

[Myk Melez [:myk] [@mykmelez]]

Malcolm's right about the space issue, which will be fixed by bug 180635.  The
other issue is a bug in the design.  We should do the following:

Review cancelled by requester: mail to requestee.
Review cancelled by requestee: mail to requester.
Review cancelled by someone else: mail to both requester and requestee.

Comment 3

[Myk Melez [:myk] [@mykmelez]]

Removing dependency on regressions meta-bug, since this isn't one, and adding
dependency on Request Tracker clean-up meta-bug, since this is an RT issue.

Comment 4

[Frédéric Buclin]

*** Bug 214179 has been marked as a duplicate of this bug. ***

Comment 5

[Karsten Düsterloh]

*** Bug 317621 has been marked as a duplicate of this bug. ***

Comment 6

[Karsten Düsterloh]

Can we somehow get some traction on this bug?
Having to visit Bugzilla or check request.cgi before realizing that a review
request has already been cancelled by the requester is really a waste of time! :-/

Comment 7

[J. Paul Reed [:preed]]

Kick all my Bugzilla bugs back to the component default owner.

Comment 8

[Frédéric Buclin]

*** Bug 336411 has been marked as a duplicate of this bug. ***

Comment 9

[Frédéric Buclin]

We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.