Closed Bug 505973 Opened 16 years ago Closed 16 years ago

EVT_BUG_CREATED should be set for existing users

Categories

(Bugzilla :: Email Notifications, defect)

defect
Not set
major

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: Wurblzap, Unassigned)

Details

(Keywords: regression)

When upgrading to a release after bug 417290, assignees with pre-existing accounts don't get notified of new bugs any more. This is because EVT_BUG_CREATED is unset for all roles. When upgrading, existing users should get the event set for all roles where they have EVT_ADDED_REMOVED set.
Flags: blocking3.4?
What means pre-existing accounts? EVT_BUG_CREATED doesn't interfere with EVT_ADDED_REMOVED, and so EVT_ADDED_REMOVED will be set and you will get notifications accordingly.
Before, I received "New Bug" notifications according to my EVT_ADDED_REMOVED setting. Now, I don't get any more, because EVT_BUG_CREATED was added, and it isn't set. Everybody who already has an account must now go ahead and set EVT_BUG_CREATED manually. EVT_BUG_CREATED must be set in checksetup.pl for existing accounts, and its initial value must be the same as EVT_ADDED_REMOVED (for each combination of user and role).
I cannot reproduce in 3.4rc1. I have a user with all email prefs turned off except "I'm added to or removed from this capacity", which is the email pref you say is broken. I create a new bug with this user as assignee, and he correctly gets bugmail. As there is no other email pref turned on, this is the one which triggers bugmail. So this is working fine.
EVT_ADDED_REMOVED encapsulates EVT_BUG_CREATED (if EVT_BUG_CREATED, then always EVT_ADDED_REMOVED), so WORKSFORME.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Flags: blocking3.4?
Status: RESOLVED → VERIFIED
Target Milestone: Bugzilla 3.4 → ---
You need to log in before you can comment on or make changes to this bug.