SLA does not populate when Priority Name is Numeric

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

When you use numerical values for your Priorities in your Jira instance you are noticing that the SLAs are not populating on the Jira Issues. Why is that?

đź’ˇ As a bit of background, when a priority clause is used in a JQL, the operand value can either be the name of the priority or the databaseID of the Priority.

However, when the Priority Name is Numeric, JQL is interpreting the priority value as the ID and not the name of the Priority. When this happens no JQL Filters will match and no SLA will show up on the Jira Issue.

Solution

Environment

  1. Have your Priority Names all be numerical values

  2. Ensure your time goals for an SLA use JQL for the Priority

  3. Create an Issue and ensure it meets a Start Condition for the SLA, as well as the JQL of a time goal

    1. The SLA will not populate on the Jira Issue

Environment Setup To Replicate Issue

(Auto-migrated image: description temporarily unavailable)

Workaround Solution

As a workaround to resolve this issue, you can add double quotes to the Priority value, such as:

  • priority=1 => priority="1"

Environment Setup To Resolve Issue

(Auto-migrated image: description temporarily unavailable)
Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.