Notification prefs (cc changes for cced bugs) don't work

RESOLVED FIXED in Bugzilla 2.12



17 years ago
5 years ago


(Reporter: BenB, Assigned: Tara Hernandez)


Bugzilla 2.12




17 years ago
1. Change your prefs not to get mail for cc field changes for bug you are cced on.
2. Make such a change on auch a bug.

Actual result:
Do do get mail for the change.

Expected result:
No mail.

Comment 1

17 years ago
Hmmm... now that's the exact opposite of what I've been hearing (see bug 71798).
Is CC the only change you're making?

Comment 2

17 years ago
Yes, I left everything else unchanged, i.e. enabled.
It appears to me that whenever someone changes the cc field on a bug I'm
interested in, I now get a message sent using the old email tech. I've been
signed up for the new e-mail tech for months now. I'm not supposed to get cc
changes either.

Other changes use the new e-mail tech.

I tried turning going to old tech, then new tech to see if that would clear
things out, but it hasn't.

Is this what others are seeing?

Comment 4

17 years ago
I'm getting this as well.

Comment 5

17 years ago
Eric, Matthew: that would be bug 71625.
This bug was originally about something different, please let's keep the focus
Target Milestone: --- → Bugzilla 2.12

Comment 6

17 years ago
Ben, there have been a few changes to the filtering code recently... are you
still seeing this behaviour?
More changes went into the email prefs and notification code this morning, and has updated.  Please try to duplicate this and let me know 
if you can or not.  If no one can duplicate this still within a week, I will 
assume the other checkins related to notifications fixed it.
per my previous comment (it's been just about a week), I'm assuming this is 
fixed.  If anyone can duplicate it again, please reopen.
Last Resolved: 17 years ago
Resolution: --- → FIXED
Moving closed bugs to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → unspecified
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.