Closed
Bug 1335012
Opened 7 years ago
Closed 7 years ago
sometimes i don't get e-mail for changes to bugs in a component i watch
Categories
(bugzilla.mozilla.org :: Extensions, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: bhearsum, Unassigned)
References
Details
I'm not certain whether this in a general Bugzilla issue or a BMO issue, but I'll file here since I don't use any of the BMO-specific mail stuff. I watch the "Balrog: Backend" and "Balrog: Frontend" components of the "Release Engineering" product on BMO. Twice in the past week I've noticed missing mail after someone has made a comment. First for https://bugzilla.mozilla.org/show_bug.cgi?id=1326074#c1, and then for https://bugzilla.mozilla.org/show_bug.cgi?id=1304561#c1. Others have responded quickly after those comments, so clearly _some_ e-mail is being sent for them. I get lots of other e-mail for these components every day, so the component watch doesn't seem to be broken in general. However, I noticed that in both cases above, I'm not the creator of the bug, nor on the cc list, so I wonder if that plays a factor. Here's what my e-mail preferences look like: https://people-mozilla.org/~bhearsum/sattap/a6302f54.png
Assignee: email-notifications → nobody
Component: Email Notifications → Extensions: ComponentWatching
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
Reporter | ||
Comment 2•7 years ago
|
||
I'm beginning to think that component watching is completely busted. I have received zero e-mail about https://bugzilla.mozilla.org/show_bug.cgi?id=1334100, which has multiple comments over different days.
Comment 3•7 years ago
|
||
this turned out to be a misconfiguration on ben's part, we can later evaluate if we need to change component watching to have a higeher precedence than normal email settings.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Updated•5 years ago
|
Component: Extensions: ComponentWatching → Extensions
You need to log in
before you can comment on or make changes to this bug.
Description
•