How to Sort Your Jira Backlog by Priority Automatically

Why sorting by native Priority doesn't work

Jira's built-in Priority field is a single-select list with five values. Sorting by it does exactly what it says — it groups issues into five buckets. Within each bucket the order is whatever Jira decides (usually rank or created date). The field has two structural problems that no amount of sorting fixes:

• Coarse granularity. Five values can't differentiate the top 10 issues. If you have 30 "High" items, you still need to decide which one to pull first.
• Label inflation. Once a few items are "Highest", everything new also wants to be "Highest" — otherwise the requester worries it won't get done. The field drifts upwards until it stops conveying information.

A real ranked backlog needs a continuous numeric score per issue, so two items can be compared on a number instead of arguing about a label. The classic frameworks for that are RICE, WSJF, and ICE.

Three frameworks that produce a number

RICE

RICE = (Reach × Impact × Confidence) ÷ Effort. Designed at Intercom for product teams ranking user-facing features. Reach is "how many users in a period", Impact is a scale 0.25–3, Confidence is a percentage, Effort is person-months. The output is a number — typically 1 to 1000+ — that can be compared across the entire backlog.

See: RICE Scoring in Jira: The Complete Setup Guide.

WSJF

WSJF = (Business Value + Time Criticality + Risk Reduction) ÷ Job Size. The SAFe standard for sequencing the ART backlog, scored on a Fibonacci scale. Output is typically 0.1 to 10+. Useful when "value" has to be decomposed because the team is weighing economic value against time pressure.

See: WSJF in Jira: SAFe Prioritization Without Spreadsheets.

ICE

ICE = Impact × Confidence × Ease. The fastest of the three — three dimensions, no division. Output is typically 1 to 1000. Right for growth teams running experiments where speed of decision matters more than depth.

See: ICE Scoring in Jira: Fast Prioritization for Growth Teams.

Not sure which to pick? The RICE vs WSJF vs ICE comparison walks through the decision tree.

How to sort by a real priority score in Jira

The mechanics are the same regardless of which framework you choose. You need a numeric custom field on every issue, a way to populate it consistently, and a backlog or list view sorted by that field.

1. 1
   Add a numeric score field to your project. Either a plain Jira number custom field (you compute the score elsewhere and paste it in), or a field type from a scoring app that calculates the score from dimension sliders.
2. 2
   Add the field to your issue screens. Jira Settings → Work items → Screens. Add the score field to the create, edit, and view screens of every relevant screen scheme.
3. 3
   Populate the score on each issue. Either manually, or via a Rovo AI agent that proposes values, or in bulk via the import path.
4. 4
   Add the score field as a column in the backlog or list view. Click the column-picker icon, search for the field name, enable it.
5. 5
   Click the column header to sort descending. The highest-scoring issue is now at the top.

Doing it with Priority Scoring

Priority Scoring for Jira is one Marketplace app that builds steps 1 and 3 in for you. It registers three custom field types — Priority Scoring — RICE, Priority Scoring — WSJF, and Priority Scoring — ICE — that each store dimension values, calculate the score live, and store the result as a sortable numeric value on the issue.

The setup once installed:

1. Create the field — Jira Settings → Work items → Fields → Create new field. Search priority scoring, pick the framework, name it.
2. Add to screens — Jira Settings → Work items → Screens. Add the field to the project's screen.
3. Score issues — open an issue, click the score field, drag the dimension sliders. The score updates live. Save with the checkmark.
4. Open the Priority Ranking tab in the app — every scored issue in the project, sorted by score descending, with issue key, summary, type, status, sprint, due date, and score bar. Export to CSV from there if you need to drop it into a steering deck.

Sorting via JQL

Once a numeric custom field exists — whether from an app or a plain Jira number field — JQL supports ORDER BY on it. This is the cleanest way to drive filters, gadgets, and exports:

project = "MYPROJ"
  AND statusCategory != Done
  ORDER BY "Priority Scoring — RICE" DESC

Save the query as a filter. You can then:

• Subscribe to it for a weekly digest email of the top N items.
• Use it as the source for a Filter Results dashboard gadget.
• Reference it in the Confluence Jira Issues macro to embed the ranked list on a project page.

Keep the native Priority field — for one thing

The native Jira Priority field doesn't have to go. It still has one role it does well: severity. Use it to mark incident severity or production-impacting urgency (Highest = page someone, Lowest = next quarter's polish). Use the numeric score field for everything else — roadmap decisions, sprint planning, backlog grooming.

Those are two different questions. Severity is "how bad if we don't do it"; priority score is "how valuable per unit of effort". They should produce different orderings on purpose.

Frequently asked questions