Short definition
Priority in Jira is a built-in field that captures how urgently an issue should be worked - Highest, High, Medium, Low, Lowest by default, configurable per instance. Priority is for scheduling decisions (what do we do next?), not for measuring user impact (use Severity for that). Priority schemes can assign different priority sets to different issue types or projects.
Why priority is confusing
Most Jira instances accumulate ambiguity around the Priority field over time because:
- Different teams interpret the same value differently. One team’s “High” is another team’s “Highest.”
- The default five values (Highest / High / Medium / Low / Lowest) carry no semantic anchor - what does “Medium” actually mean?
- The field gets used both as user-facing severity (“how bad is it for the customer?”) and as engineering scheduling weight (“how soon do we work it?”), even though those are different things.
The clearest setups make Priority a pure scheduling field and add a separate Severity custom field for user impact. That gives:
- Severity - measured at the moment the bug is reported, mostly objective: S1 outage, S2 major feature broken, S3 minor functionality, S4 cosmetic.
- Priority - assigned by triage based on severity plus business context (which customer, which release window, what else is in flight). Can move over time.
Priority schemes
A Priority Scheme lets different projects use different priority lists. Common cases:
- A customer-support project uses an SLA-oriented list (P1 / P2 / P3 / P4).
- An engineering project uses an effort-oriented list (Now / Next / Later).
- An R&D project uses a coarse list (High / Low only).
Schemes are configured globally and assigned per project under Settings -> Issues -> Priority schemes (Cloud) or in admin (Data Center, where the feature is more limited).
Priority and SLA
Jira Service Management uses Priority as a key SLA driver. SLA configurations attach response-time and resolution-time targets per priority. A typical pattern: P1 has 30-minute response and 4-hour resolution targets; P4 has next-business-day response and no resolution target.
For SLA-driven projects, the Priority field should be required on the Create screen and ideally guarded by a workflow validator on the triage transition so nobody can move an issue out of New without setting it.
Default values and Create-screen design
If the project doesn’t pick a sensible default for Priority on the Create Issue screen, Jira assigns the global default (often “Medium”). Reporters who skip the field accept whatever the default is. Two common patterns to avoid garbage data:
- Make Priority required on the Create screen via Field Configuration.
- Pick the lowest sensible value as the default - “Low” rather than “Medium” - so reporters who skip the field don’t accidentally elevate work.
Common questions
What is priority in Jira?
Priority in Jira is a built-in field that captures how urgently an issue should be worked - Highest, High, Medium, Low, Lowest by default, configurable per instance. Priority is for scheduling decisions (what do we do next?), not for measuring user impact (use Severity for that). Priority schemes can assign different priority sets to different issue types or projects.
What's the difference between priority and severity in Jira?
Severity measures user impact (how broken is it?). Priority measures scheduling urgency (when do we fix it?). A low-severity, high-priority bug is rare; a high-severity, low-priority bug usually means a workaround exists. Most well-run bug processes use both fields - severity stays roughly fixed once set, priority can move based on business context.
Can I add a custom priority value in Jira?
Yes. Admins can edit the global priority list under Settings -> Issues -> Priorities. Be aware that priorities are global on Data Center - they apply to every project. On Cloud, priorities can be scoped via Priority Schemes that select which subset of the global list applies to a given project.
Should priority be set by the reporter or by triage?
Most teams ask the reporter to set an initial priority, then let triage adjust it during the formal bug review. A common pattern is to default new bugs to 'Medium' on the Create screen so reporters who skip the field don't accidentally file everything as 'Highest.'