Open Bug 72075 Opened 25 years ago Updated 11 years ago

don't send email about dependency change when email about dependent bug was already sent

Categories

(Bugzilla :: Email Notifications, enhancement, P2)

2.13
enhancement

Tracking

()

People

(Reporter: st.n, Unassigned)

References

Details

Suppose bug A depends on bug B and I'm on the Cc list of both bugs. Now suppose bug B changes state, say to resolved/fixed. I get a bugmail about this because I'm on the Cc list. But I also get a bugmail for bug A because a dependent bug changed state, and I think this mail should be omitted for all recipients of the bug B bugmail, because they already got notified.
Blocks: 53044
But the question is, do they remember at the time they get the bugmail, that it's a blocker, and which bug is the dependent?
If we eventually go down the route of allowing a user to specify that field X appears on every notification, regardless, then this behaviour might become beneficial. And AFAICS, this question applies to duplicate marking too.
Target Milestone: --- → Future
See also bug #71710.
Severity: normal → enhancement
Priority: -- → P4
Target Milestone: Future → Bugzilla 2.16
Also, although they know that bug B was fixed, they might have forgotten bug A was blocked by it.
Mass moving to new product Bugzilla...
Assignee: tara → jake
Component: Bugzilla → Email
Product: Webtools → Bugzilla
Version: Bugzilla 2.11 → 2.13
No longer blocks: 53044
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Changing default owner of Email Notifications component to JayPee, a.k.a. J. Paul Reed (preed@sigkill.com). Jake will be offline for a few months.
Assignee: jake → preed
Re: comment 1, comment 4 Maybe it should send the email for bug A, but include _all_ changes in bug B: <example> http://bugzilla.mozilla.org/show_bug.cgi?id=187990 Bug 187990 depends on bug 189543, which changed state. Bug 189543 Summary: Mailviews: View dropdown menu items should be in View:Messages Menu http://bugzilla.mozilla.org/show_bug.cgi?id=189543 What |Old Value |New Value ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From sspitzer@netscape.com 2003-04-30 00:37 ------- fixed, this has r/sr=bienvenu, a=sspitzer </example> Now, this leaves the question of what ought to be put in the subject line.
Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Assignee: preed → email-notifications
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
I would seriously like to see this in 4.0.
Priority: P4 → P2
Whiteboard: [roadmap: 4.0]
Target Milestone: --- → Bugzilla 4.0
I would not enjoy this change. Maybe it would be okay if bug 8527 or bug 593500 were fixed first.
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.
Target Milestone: Bugzilla 4.4 → ---
Whiteboard: [roadmap: 4.0]
There are two essentially different ideas here. 1. Suppress the email from the dependency change (the original proposal). To control this, we would add another "but not when" condition to the dependency email matrix - maybe something like "The change was made via a dependent bug, about which an email has already been sent to me". 2. Consolidate multiple notifications generated by a single action into a single email (the lines of comment 8). I suppose this would be a single account-level pref (unless someone can think of a way of breaking it down that would work). That said, it could be a three-way setting: (a) never consolidate (as happens at the moment) (b) when a change is made to a single bug, consolidate notifications that bug and its dependent bugs (c) always consolidate (to generate a single email when Change Several Bugs at Once is used) But idea 2 should probably be a separate RFE.
You need to log in before you can comment on or make changes to this bug.