What is an X-Priority?
The X-Priority is used to indicate the importance of a message. Microsoft
...
supports 5 X-Priority levels https://
...
...
...
/en-us/openspecs/exchange_server_protocols/ms-oxcmail/2bb19f1b-b35e-4966-b1cb-1afd044e83ab with 1 being the highest and 5 the lowest.
There is a default Priority Scheme for all Projects that don’t have a defined Priority Scheme. It has the default 5 priority levels from 1-5. However, Priorities and Priority Schemes can be created and applied to a given Project. A created Priority Scheme can contain any amount of priorities starting from 1.
Due to a Priority Scheme potentially holding more than 5 Priorities matching the 5 Priority levels that Microsoft allows, JEMH has to make changes to decide which Priority should be used for a message.
How JEMH works with X-Priorities:
JEMH
Note: If the user selects chooses an X-Priority that is greater than 5, the lowest priority that is available will be used.
Example use of implementation:
Example Case Results:
Case with 1:
...
Number of Priorities
...
Chosen Priority
...
Result Priority
...
1
...
1
...
1
...
2
...
1
...
1
...
3
...
1
...
1
...
4
...
1
...
1
...
5
...
1
...
1
...
6
...
1
...
1
...
7
...
1
...
1
...
8
...
1
...
1
...
9
...
1
...
1
...
10
...
1
...
1
Case with 5
...
Number of Priorities
...
Chosen Priority
...
Result Priority
...
1
...
5
...
1
...
2
...
5
...
2
...
3
...
5
...
3
...
4
...
5
...
4
...
5
...
5
...
5
...
6
...
5
...
6
...
7
...
5
...
7
...
8
...
5
...
8
...
9
...
5
...
9
...
10
...
5
...
10
Case with 3
When enabled through Profile > Issue > Use Mail X-Priority Priority, JEMH will map this to an actual Priority defined in the Project Priority Scheme.
How JEMH works with X-Priority header
| Status | ||||
|---|---|---|---|---|
|
Starting in the above versions, JEMH will make use of the priorities set on a per project basis through a Priority Scheme. As the number of Project Priorities can be any number, the 5 X-Priorities map into the set of available Jira priorities. We have ensured that an X-Priority value of 1 always maps to the highest Jira priority and 5 always maps to the lowest Jira priority. Values 2-4 will spread between the highest and lowest priority depending on how many there are. If the value supplied has been deliberately set above 1-5, it will be tested for an exact match on a Jira priority ID, non-matches are treated as lowest priority.
How X-Priority values map to Jira priorities
The tables below show how X-Priority values map to project priorities. The selected index indicates the target priority from the available project priorities (1 = first/highest).
X-Priority = 1
Project Priorities | Selected Index |
|---|---|
1 | 1 |
2 | 1 |
3 | 1 |
4 | 1 |
5 | 1 |
6 | 1 |
7 | 1 |
8 | 1 |
9 | 1 |
10 | 1 |
X-Priority = 2
Project Priorities | Selected Index |
|---|---|
1 | 1 |
2 | 1 |
3 | 1 |
4 | 1 |
5 | 2 |
6 | 2 |
7 | 2 |
8 | 2 |
9 | 2 |
10 | 3 |
X-Priority = 3
Project Priorities | Selected Index |
|---|---|
1 | 1 |
2 | 2 |
3 | 2 |
4 | 3 |
5 | 3 |
6 | 4 |
7 | 5 |
8 | 5 |
9 | 6 |
10 | 6 |
X-Priority = 4
Project Priorities | Selected Index |
|---|---|
1 | 1 |
2 | 2 |
3 | 3 |
4 | 4 |
5 | 4 |
6 | 5 |
7 | 6 |
8 | 7 |
9 | 8 |
10 | 8 |
X-Priority = 5
Number of Priorities | Chosen Priority | Result Priority |
|---|---|---|
1 |
...
5 | 1 |
2 |
...
5 | 2 | |
3 | 5 | 3 |
...
4 | 5 | 4 |
...
5 |
...
5 | 5 |
...
6 |
...
5 | 6 |
...
7 |
...
5 | 7 |
...
8 | 5 | 8 |
...
9 | 5 | 9 |
...
10 |
...
6
...
10
...
3
...
6
Feature Improvement:
...
5 | 10 |