mail handler is not using the default priority

[JasonH Arvato]

Issues created by mail handler are not getting the default priority from the project's priority scheme but instead they get the default priority from the default priority scheme.

The mail handler is configured just to create issues in the project with high/medium/low, and since medium is the default in that scheme I'd expect to see all issues from mail created with medium.  But it creates them with a priority of 'trivial' for some reason.

[Petter Gonçalves]

Hello @JasonH Arvato

Thank you for reaching out.

Indeed, JIRA does not respect the default priority configured in your priority schemes when creating issues using the mail handler. We have a bug reported to fix this behavior:

- Incoming Mail Handler does not respect the default priority in Priorities Scheme 

Feel free to vote and watch the bug to receive notifications about any updates or its fix implementation.

For now, since the "default priority" selected is the one in the middle of the priority scheme, you can follow the workaround below:

• You can rearrange the order of the priorities to set the one you want as default to be in the middle on the global list of priorities at Jira Administration > Issues > Priorities.
  OR
• You can use the completely free add-on Workflow Enhancer, which adds Universal postfunction to workflows that allows you to evaluate values from fields, and you can use this in the Create transition, adding a post function to evaluate if the priority is out of the project's Priorities, and to set the priority to the one you want as default. For example, setting the result of the evaluation as FALSE, from the following, should do the trick: {code} {Priority}
  == "Critical" || {Priority} == "Major" || {Priority} == "Minor" || {Priority} == "Trivial" || {Priority} == "Blocker" {code}

Let us know if you still have any questions.

[Yves Martin]

Simply unbelievable... Priority schemes have been introduced in JIRA 7 and now Mail Handler is just broken (setting invalid field value in issue) ! Already 1.5 year waiting for a proper fix !