326943 - Add email pref for I want to receive email when there are changes to bugs in the dependency tree

Status: NEW

(Bugzilla :: Email Notifications, enhancement)

Description

[Douglas Calvert]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060207 Debian/1.5.dfsg+1.5.0.1-1 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060207 Debian/1.5.dfsg+1.5.0.1-1 Firefox/1.5.0.1

There should be a email_pref that lets users request email notification of changes to dependent bugs. Currently there is a pref "The dependency tree changes" this only emails the user when they are the assignee/cc/qa/.. of a bug and there is an addition/deletion/statuschange of a bug. I would like to receive email when I am the reporter/cc/qa/... of a bug and there are comments/attachments/new deps. THe wording of the email_pref is a little tricky but something like:

"there are changes to bugs in the dependency tree"



Reproducible: Always

Comment 1

[Douglas Calvert]

I predicted that this would be a duplicate and i think it is very similar to bug 93957. The details of 93957 should be altered a bit imho. the summary for bug 93957 is "Email notification on comments to bugs depended on by voted bugs" but the description is:

Some people might appreciate recieving comments posted to other bugs when those
bugs block a bug they've voted on.  This would of course have to be a
preference.  (Probably off by default.)  This is related to bug 92440.

and then bug 93957 comment 1 says:

Actually, I could see theis being useful as the owner of a bug or when on the
CC list as well...  It could probably be accomplished without too much difficulty
by simply CC'ing interested parties to the correct bugs.  (Which in turn, could
end up CC'ing them to other bugs further down the tree.)  This way if a bug
being depended on really isn't of interest, it can just be un-CC'd from.  And
it shouldn't introduce too much bloat into bugzilla.

I think that a change to the summary and a clarification of the description in bug 93957 should be enough to dupme...

Comment 2

[Max Kanat-Alexander]

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

Comment 3

[Robert Pollak]

Is my bug 1218606 a duplicate?