6999 - Bugzilla should send "fixed" mails to duplicate bugs

Status: RESOLVED INVALID

(Bugzilla :: Email Notifications, enhancement, P3)

Description

[Roland Mainz]

Current state: Bugzilla marks bugs as "duplicate", no futher mail is sent.

Should be: Duplicate bug reporters should be CC:'ed to the main bug (e.g. the
first bug report about this particular problem),

AND/OR

if the bug has been fixed, all duplicate bugs should be marked as fixed and
mails to the bug reporters should be sent that their reported problema are gone.

Comment 1

[Daniel Roberts]

I concur that the duplicate bug reporters should be CC:'ed to the main bug.
Speaking for myself, I currently do add myself to the CC: line in the main bug
whenever I receive e-mail notification of a duplicate bug.  But it would be more
convienient (and save me some time) if this happened automatically, so I
wouldn't have to enter my e-mail address in the main bug everytime.  But if this
enhancement is made, I think Bugzilla should then also tell the duplicate
reporter that he has been added to the CC: line of the main bug when the
duplicate bugs are marked, just so the reporter is aware of this.

One little side note--while I agree with you about the first part, I'm not sure
I agree with the second part... If the first part of your idea were implemented,
and the duplicate reporters are then put on the CC: line automatically in the
main bug, why then notify people more than once that their reported bug is
fixed?  Once should be enough, IMHO, especially considering that the whole
purpose of marking DUPLICATE in the first place is to allow people to make sure
each bug is properly identified only once and help reduce spam.  So I think the
first part of your suggestion is really all that's needed.

Comment 2

[Daniel Roberts]

Come to think of it, it might be nice also to automatically CC: people who add
additional comments, the way I just did...  This might be a little more
questionable though, as not everyone may want to have this happen
automatically.  Perhaps this should be another individual configuration option
if it is added?

Comment 3

[Matthew Tuck [:CodeMachine]]

I agree with (a).  The reporter and any people on cc should be moved to the main
bug.  I have filed bug #11319 on the auto-add to CC issue.

Comment 4

[Terry Weissman]

[e-mail] is the new owner of Bugzilla and Bonsai.  (For details,
see my posting in netscape.public.mozilla.webtools,
news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)

Comment 5

[Jesse Ruderman]

Looks like this depends on bug 25693, storing a table of duplicates.

Comment 6

[Stephan Niemz]

Adding default QA contact to all open Webtools/Bugzilla bugs lacking one.
Sorry for the spam.

Comment 7

[Dave Miller [:justdave]]

The reporter of a bug is now automatically added to the CC of the original when a 
bug is marked as a dupe.  Does that solve this problem adequately?

Comment 8

[Daniel Roberts]

I would think so.  Does everyone agree?

Comment 9

[Matthew Cline]

What about everyone whose added themselves to the CC list?  Shouldn't
they be auto-added to the CC list of the original bug?

Comment 10

[Jacob Steenhagen]

The CC List was discussed but decided against.  I don't remember the exact
reason for this decision.

Comment 11

[Stephen Rasku]

Since the reporter is now subscribed to the duplicated bug, can we close this
now?

Comment 12

[Matthew Tuck [:CodeMachine]]

This is not just about the reporter.

Comment 13

[Christian Reis]

New product: bugzilla.

Comment 14

[jeff givens]

Is this still open? A report I did, 166683, was marked as a duplicate as 165081.
My email showed up in the cc: of tis report. 165081 was marked as a duplicate of
101055. My cc: did not transfer to this report. It is there now but I added it
as I made a comment to 101055.

I suspect the problem is that the moving of the cc: happens only when the "mark
as duplicate" action is taken. Since 165081 had already been marked as a
duplicate my email never transferred to the end of the chain, 101055.

Comment 15

[J. Paul Reed [:preed]]

I'm gonna mark this as closed/invalid.

It looks like there's some discussion (bug 108983) about whether this is the
proper action to take. Either way, that will fix this bug by adding those people
to the Cc list, and thus they'll get the bug mails, and that's the right (tm)
solution; IOW, this isn't an email notifications issue, per se.

Tara, or anyone else: if you have objections, please respond below.