Closed Bug 45230 Opened 25 years ago Closed 17 years ago

On process_bug.cgi, say why people are being sent notifications.

Categories

(Bugzilla :: Email Notifications, enhancement, P3)

Product:
Bugzilla
Component:
Email Notifications
Type:
enhancement

Tracking

()

Status:
VERIFIED WONTFIX

People

(Reporter: CodeMachine, Unassigned)

Details

(Whiteboard: Future-Target)

Currently process_bug.cgi just gives a list of people getting notifications. If it did something like: Sending to QA contact: b@b.com Sending to assignee: b@b.com Sending to reporter: a@a.com Sending to people on CC list: c@c.com, d@d.com Sending to people who have voted for this bug: c@c.com, e@e.com Sending to watchers: f@f.com (watching a@a.com), g@g.com (watching a@a.com) This, along with bug #26194, should help prevent various "why are we/they getting these notifications" bugs that get submitted.
Whiteboard: Future-Target
moving to real milestones...
Target Milestone: --- → Future
-> Bugzilla product, Email component, reassigning.
Assignee: tara → jake
Component: Bugzilla → Email
Product: Webtools → Bugzilla
Version: other → unspecified
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
Kick all my Bugzilla bugs back to the component default owner.
Assignee: preed → email-notifications
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Future → ---
Duplicating email addresses is meaningless to me, and you probably don't care that much about why a user gets notifications. You could check that yourself by looking at the bug itself (reporter, assignee, QA contact voters and CC list). If the user is not in one of these fields, then he is a watcher. Marking as WONTFIX as this RFE got no attention in almost 8 years.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WONTFIX
Agreed, this would be a pretty significant effort and would probably just degrade the UI.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.