Closed Bug 652419 Opened 14 years ago Closed 13 years ago

No reason given for email notification

Categories

(bugzilla.mozilla.org :: Extensions, defect)

Product:
bugzilla.mozilla.org
Component:
Extensions
Version:
Production
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: jdm, Assigned: glob)

References

Details

I just received an email from a component that I'm not watching, with no users CCed that I watch. The reasons given: >-- >Configure bugmail: https://bugzilla.mozilla.org/userprefs.cgi?tab=email >------- You are receiving this mail because: ------- This is suboptimal.
This is due to a bmo customization.
Assignee: email-notifications → nobody
Blocks: bmo-regressions
Component: Email Notifications → Bugzilla: Other b.m.o Issues
Product: Bugzilla → mozilla.org
QA Contact: default-qa → other-bmo-issues
Version: 4.0 → other
Agreed. I'm seeing CC field changes, which I've explicitly disabled in user watching, so this must be coming from component watching.
Assignee: nobody → gerv
Component: Bugzilla: Other b.m.o Issues → Governance
QA Contact: other-bmo-issues → governance
Assignee: gerv → nobody
Component: Governance → Bugzilla: Other b.m.o Issues
QA Contact: governance → other-bmo-issues
Depends on: 652400
Component: Bugzilla: Other b.m.o Issues → Component Watching
Product: mozilla.org → bugzilla.mozilla.org
QA Contact: other-bmo-issues → bmo-comp-watch
Version: other → Current
Assignee: nobody → glob
Status: NEW → ASSIGNED
this should be fixed by the changes in bug 652400
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
This happened again today. Maybe it's because I watch "Core: Networking" and the affected component is "Core: Networking: Domain Lists"?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #4) > This happened again today. Maybe it's because I watch "Core: Networking" and > the affected component is "Core: Networking: Domain Lists"? josh, can please raise a new bug rather than reopening an existing bug. thanks :)
Status: REOPENED → RESOLVED
Closed: 14 years ago → 13 years ago
Resolution: --- → FIXED
Component: Extensions: ComponentWatching → Extensions
You need to log in before you can comment on or make changes to this bug.