Closed
Bug 453792
Opened 16 years ago
Closed 16 years ago
Bugzilla should differentiate in headers (X-Bugzilla-Type) between new and changed mail
Categories
(Bugzilla :: Email Notifications, enhancement)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.4
People
(Reporter: gerv, Assigned: gerv)
Details
Attachments
(1 file)
946 bytes,
patch
|
Wurblzap
:
review+
|
Details | Diff | Splinter Review |
People would like to filter email based on whether it's the notification of a new bug or whether it's an update on an existing one. Yes, you can parse the Subject line for "] New:", but that would break for localizations and there's an (OK, small) risk of false positives. Currently: X-Bugzilla-Type: newchanged Suggested: X-Bugzilla-Type: new or X-Bugzilla-Type: changed This is a one-line change to newchangedmail.txt.tmpl. Gerv
Assignee | ||
Comment 1•16 years ago
|
||
The obvious patch. Gerv
Assignee: email-notifications → gerv
Status: NEW → ASSIGNED
Attachment #337008 -
Flags: review?(justdave)
Comment 2•16 years ago
|
||
Comment on attachment 337008 [details] [diff] [review] Patch v.1 r=Wurblzap by inspection. This will break existing filters triggered by "newchanged", so it may need to be relnoted.
Attachment #337008 -
Flags: review+
Assignee | ||
Comment 3•16 years ago
|
||
Dave, Max, I did this for bz. Can we get it on b.m.o. too? Gerv
Comment 4•16 years ago
|
||
(In reply to comment #3) > I did this for bz. Can we get it on b.m.o. too? Can you get it committed to Bugzilla 3.2 branch? Much easier just to pull from upstream rather than taking a local bmo-only patch.
Assignee | ||
Comment 5•16 years ago
|
||
OK, I'll try. Let's see what happens when I set this flag... Gerv
Flags: approval3.2?
Updated•16 years ago
|
Comment 6•16 years ago
|
||
Unfortunately, those headers represent a sort of "API" and I can't change them on the branch this close to a release.
Severity: normal → enhancement
Flags: approval?
Flags: approval3.2?
Flags: approval3.2-
Flags: approval+
Updated•16 years ago
|
Attachment #337008 -
Flags: review?(justdave)
Updated•16 years ago
|
Target Milestone: Bugzilla 3.2 → Bugzilla 3.4
Assignee | ||
Comment 7•16 years ago
|
||
Surely before a major release (as opposed to after) is the right time to change an API? I still want this for b.m.o., though. Gerv
Comment 8•16 years ago
|
||
But we already released RC1.
Assignee | ||
Comment 9•16 years ago
|
||
Checking in template/en/default/email/newchangedmail.txt.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/email/newchangedmail.txt.tmpl,v <-- newchangedmail.txt.tmpl new revision: 1.12; previous revision: 1.11 done Gerv
Updated•16 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 10•15 years ago
|
||
Added to the release notes for Bugzilla 3.4 in bug 494037.
Keywords: relnote
You need to log in
before you can comment on or make changes to this bug.
Description
•