Open
Bug 148874
Opened 23 years ago
Updated 12 years ago
document in the code why overlapping email preferences happen to work
Categories
(Bugzilla :: Email Notifications, defect, P3)
Tracking
()
NEW
People
(Reporter: myk, Unassigned)
Details
I said this over in bug 146261, comment 5:
---
No, because the code containing the elsifs runs once per change, so no change
matches more than one condition. The only exception is status changes to
resolved or verified, which match both the 'The bug is resolved or verified' and
the 'Priority, status, severity, and/or milestone changes' preferences.
Since the former preference is more specific than the latter, however, it should
override it, so the elsifs work in that situation as well (but this should be
documented).
---
Comment 1•23 years ago
|
||
Erm, shouldn't that be document in the UI?
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.18
Reporter | ||
Comment 2•23 years ago
|
||
No, I mean in the code, where we accidentally get the desired result (leaving us
susceptible to bug exposure if this code is ever hacked, hence my statement
about documenting it).
Comment 3•23 years ago
|
||
OK, well, it's also a UI issue, that people might think that status changes to
resolved or verified can get matched by either.
Comment 4•21 years ago
|
||
These unloved bugs have been sitting untouched since June 2002 or longer. If
nobody does anything else to them, they certainly won't make 2.18
Retargetting to 2.20. If you really plan to push them right now, you might pull
them back in.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Comment 5•20 years ago
|
||
As preed is no longer actively working on Bugzilla (from what I know), I somehow
doubt that this bug will make it in for 2.20. :-) If I'm wrong, feel free to
take it back and re-target it. :-)
Assignee: preed → email-notifications
Target Milestone: Bugzilla 2.20 → ---
Updated•19 years ago
|
QA Contact: mattyt-bugzilla → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•