Closed Bug 55108 Opened 25 years ago Closed 17 years ago

Create a status-update field that's separate from CC:

Categories

(Bugzilla :: Email Notifications, enhancement, P3)

enhancement

Tracking

()

RESOLVED WONTFIX

People

(Reporter: jce2, Unassigned)

References

Details

(Whiteboard: [people:cc])

There are a lot of people who cc themselves to a bug that don't really care about the discussion surrounding the bug, they just want to be notified when the bug is fixed. Therefore, some people are complaining about "spam" on bugs with large cc lists whenever someone adds a comment to the bug. Therefore, I think we should create another field that just sends e-mail when the status of the bug has been changed from NEW or ASSIGNED to FIXED. It could just send an e-mail out to those people saying "Bug# xxxxx (description), has now been fixed." That way, we won't have to worry about commenting freely on a bug without spamming people, because the only people who would remain cc'ed on a bug would be those people who actually want to read the discussion.
I like this idea. There's some related discussion in bug 7345 and bug 17464 (mostly about bcc or quiet cc). Adding this bug to tracking bug 53044.
Blocks: 53044
I think bug #17464 pretty much covers this.
In which way does that bug cover this?
Hardware: PC → All
Well, in the incarnation that eventually got checked in, it doesn't.
Maybe the appropriate way to deal with this is to allow a user to define a personal "interest class" and allow people to filter on it.
Target Milestone: --- → Future
Whiteboard: [people:cc]
No longer blocks: 53044
-> Bugzilla product
Assignee: tara → jake
Component: Bugzilla → Email Notifications
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
Isn't this fixed by our current email prefs, i.e. you can ignore comments (or anything else) and just get status updates (or anything else)?
A few months ago, I created a second bugzilla account, jruderman+whenresolved@hmc.edu, with e-mail prefs set to only notify me of status changes. I've cc'ed it on 18 bugs since then, mostly regressions where I don't expect there to be a debate about expected behavior or UI.
This sounds like the duped bug; complain if I got it wrong. *** This bug has been marked as a duplicate of 125538 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Bug 125538 is about separating "The bug is resolved or verified" in *prefs* into two or three lines. This bug is for a per-bug list of people who want to receive status update notification. Fixing bug 125538 would not fix this bug, because some people want to receive status updates on some bugs and all updates on other bugs.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
*** Bug 152010 has been marked as a duplicate of this bug. ***
*** Bug 201916 has been marked as a duplicate of this bug. ***
Jesse: you're right. I just found bug 125538 before I found this bug... thanks for correcting that.
Kick all my Bugzilla bugs back to the component default owner.
Assignee: preed → email-notifications
Status: REOPENED → NEW
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Future → ---
AFAICT, you can use the voting system to only get notifications when the bug status changes. I doubt voters are interested in anything else but bug changes. We are not going to implement another field to get only bug changes.
Status: NEW → RESOLVED
Closed: 22 years ago17 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.