Patch #2746
Send out issue priority in the email notification header
| Status: | New | Start date: | 2009-02-13 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jean-Philippe Lang | % Done: | 0% | |
| Category: | Email notifications | |||
| Target version: | - |
Description
The attached patch will send out an issue's priority with the notification email's headers. This is important for when you want to route urgent tickets differently.
priority.patch 
(938 Bytes)
Related issues
History
#1
Updated by Jean-Philippe Lang about 11 years ago
Why not use the more standard X-Priority header?
#2
Updated by Brad Beattie about 11 years ago
- Assignee set to Jean-Philippe Lang
Jean-Philippe Lang wrote:
Why not use the more standard X-Priority header?
Hrm. The header Priority has values "normal", "urgent" and "non-urgent". I can't find any RFC that defines the values of "X-Priority", but most examples I see use the values 1 through 5. While this maps up to Redmine's default priority values, other systems might have limited or extended these enumerations (e.g. my company uses "Low, Normal and Emergency". How would these modified values be mapped to X-Priority? 1, 3, 5? It's kinda vague, yeah?
I guess that's why I thought just creating a Redmine-specific priority header would be a better choice. What're your thoughts on this?
#3
Updated by Jean-Philippe Lang about 11 years ago
An other problem is that a X-Priority of 1 means urgent, whereas Redmine priorities are sorted in opposite order (1 = low).
We need to map Redmine priorities (max => 1, min => 5). Just need to retrieve the total numbers of priorities defined in Redmine.
So yes, if you have 3 priorities defined in Redmine, they would be mapped to X-Priority 1, 3 and 5.
#4
Updated by Thomas Pihl about 11 years ago
Other solution might be an extra field when defining priorities where you can choose x-priority manually for each priority. This might include an option not to send email for some priorities.
/T
#5
Updated by Jean-Philippe Lang about 11 years ago
I'd really prefer not to add an extra field just for this purpose.
Is there any problem with the solution I propose?
#6
Updated by Brad Beattie about 11 years ago
Jean-Philippe Lang wrote:
I'd really prefer not to add an extra field just for this purpose.
Is there any problem with the solution I propose?
Hrm. Yeah. Let's say we have two Redmine instances: one has priorities deferrable and normal, the other has priorities normal and emergency. How would you propose those two instances would be mapped? I don't see a way of automating this to ensure that any set of customized priorities get mapped properly to the X-Priority header. I guess that's why I suggested a Redmine-specific header.
#7
Updated by Go MAEDA over 4 years ago
- Duplicated by Feature #20443: Add Priority header to Email notifications added
#8
Updated by Go MAEDA over 4 years ago
- Related to Feature #19939: New X-Redmine-Issue-Priority header, and modification of X-Redmine-Issue-Assignee added
#9
Updated by Peter Volkov over 2 years ago
Guys what's left to do here? Can we have X-Redmine-Priority field at least and leave a question if we need standard Priority field and mapping for better times?
#10
Updated by Go MAEDA over 1 year ago
- Related to Feature #12864: If ticket was created with priority High/Urgent, send smtp-email with priority Urgent added
#11
Updated by Go MAEDA 8 months ago
- Related to Feature #31910: Add additional mail headers for issue tracker added