JIRA global priority change - Will removed priority values take the new default?

Mike Rathwell

We are going to change the global priority list (including removing a couple of values) in our JIRA instance and I am wondering if, during the change, will issues with a removed priority will take the new default?

Currently the choices in the “Priority” field are:

• Emergency
• Highest
• High
• Medium
• Low (current default value)
• Lowest

This will change to:

• Emergency
• High
• Medium
• Low
• No Priority Assigned (new default value)

My question is, to avoid a massive bulk change (or at least to mitigate it), will issues currently with a Priority value being removed, change to the new default? If so, my order of operation would be:

1. Add new value (but not remove any)
2. Do a bulk change of "Highest" to "High"
3. Remove "Lowest" and "Highest" values and re-index. The hope is that this will make the part of the bulk change from "Lowest "to "Low" as part of the re-index.
4. Set the new "No Priority Assigned" to the new default.

Let me know your thoughts. If JIRA doesn't behave in the manner of assigning removed priority values to the new default, I'll just do two massive bulk changes before removing the "-est" values.

Alexey Matveev

If you delete a priority, Jira will ask you to what priority you want to move issues, which are set to this priority. You will have to choose the required priority yourself.