Jira Backlog Health: How to Measure and Improve Your Project Quality Score

The symptoms of an unhealthy Jira backlog

Backlog health problems rarely announce themselves. They build gradually until the symptoms become impossible to ignore: sprint planning that takes three hours instead of one, constant "can someone give this more context?" questions in Slack, and the slow creep of issues that were "important" two quarters ago and haven't moved since.

The underlying causes are almost always the same few issues:

• Stale issues: Tickets that haven't been touched in weeks or months. Nobody knows if they're still relevant. Nobody wants to delete them in case they are.
• Missing descriptions: The summary says "Fix login bug." The description is empty. The developer who filed it left the team six months ago.
• No story point estimates: Sprint capacity planning becomes guesswork. Velocity tracking becomes meaningless.
• No assignees: In a Kanban flow, unassigned work is work that nobody is accountable for moving forward.
• Overdue items: Due dates were set, then missed, then never updated. The backlog now contains a graveyard of past commitments.
• No priority score: The team uses "Priority: High" for everything. When everything is urgent, nothing is.

Each of these issues is individually manageable. The problem is that they compound silently — and by the time a Scrum Master or Product Owner notices, the backlog has hundreds of issues in various states of disrepair.

What is a Board Health Score?

A Board Health Score is a single number between 0 and 100 that represents the overall quality of all open (non-done) issues in a Jira project. It's not just the backlog — it includes issues currently In Progress, In Review, or in any other active workflow state. The name "Board Health" reflects that: it's the health of everything your team is actively responsible for, not just the queue.

The score is calculated by checking each open issue against a set of quality criteria. Each criterion that fails subtracts from the total. A score of 100 means every active issue passes all checks. A score of 40 means 60% of your open work has at least one quality problem.

The score is most useful as a trend. A team that scores 62 this week and 71 next week is improving. A team that scores 80 consistently but drops to 55 after a busy release crunch has a clear signal: time to refinement.

The 8 health criteria — and what each one catches

Different teams care about different quality signals. A Scrum team without story points can't plan velocity. A Kanban team without assignees has no accountability for work in flight. Priority Scoring for Jira tracks eight criteria — you activate only the ones relevant to your workflow, per project.

Each active criterion contributes equally to the score. With four active criteria, each is worth up to 25 points. With six, each is worth up to ~16.7 points. The score always stays on a 0–100 scale regardless of how many criteria are active.

Scrum vs. Kanban profiles

Scrum and Kanban teams have fundamentally different quality concerns, so Priority Scoring provides one-click presets to configure the right criteria from the start:

• Scrum defaults: Stale Issues, Missing Description, Missing Story Points, Unscored, Overdue — the signals that block velocity planning and sprint commitment.
• Kanban defaults: Stale Issues, Missing Description, Unscored, Missing Assignee, Missing Priority, Missing Labels — the signals that block flow and routing in a continuous-delivery context.

Both presets are starting points. A Scrum team that also uses labels for area ownership can add the Missing Labels criterion without affecting the others. A Kanban team that doesn't use due dates can leave Overdue disabled entirely.

Reading the score breakdown

The raw score matters less than understanding which criterion is costing you the most points. The health panel in Priority Scoring shows a breakdown card per active criterion — with the percentage of issues currently passing and the exact number of score points being deducted.

In the example above, the team's biggest problem is clear: 52% of issues have no priority score, costing 13 points. Fixing that one criterion alone would lift the score to 80. Stale issues are the second priority. Description quality is nearly irrelevant. This breakdown converts an abstract score into a clear work order — exactly what a retrospective needs.

How to enable Board Health in Jira

1. 1
   Install Priority Scoring for Jira from the Atlassian Marketplace. The Board Health feature is included in the free trial — no extra configuration needed to access it.
2. 2
   Open the Priority Scoring dashboard via the global page in your Jira navigation. Select your project. The Board Health panel appears on the right side of the dashboard with an initial score.
3. 3
   Configure your health criteria. Click "Health Criteria…" in the toolbar. Select your project, choose the Scrum or Kanban quick preset, then toggle individual criteria on or off. Set the stale threshold (default: 60 days). Click "Save & Refresh."
4. 4
   Read the breakdown. Each criterion card shows the percentage of passing issues and the exact score penalty. Start working from the highest-penalty criterion downward.
5. 5
   (Optional) Add the Board Health gadget to your Jira dashboard. The gadget shows the score and criterion breakdown for a selected project — useful for Scrum Masters and team leads who want health visible on their Jira home dashboard without opening the full app.

Step 1: Select the project to configure health criteria for — each project can have its own set of active signals

Step 2: Enable individual criteria, use Scrum or Kanban presets, and configure the stale threshold per project

Turning a score into action

A health score is useless if it doesn't change behaviour. The most effective way to use it is to bring the breakdown into your regular ceremonies:

In sprint retrospectives

Open the Board Health panel at the end of each sprint. If the score dropped during the sprint, identify which criterion is responsible. Often it's Unscored (new issues were created without RICE/WSJF scores) or Stale (issues were deprioritized mid-sprint but not deferred or closed). This takes two minutes and makes the "process" conversation concrete.

In backlog refinement sessions

Use the criterion breakdown to focus refinement energy. If Missing Descriptions is costing 12 points, spend the first 15 minutes of refinement adding acceptance criteria to the worst offenders. The Rovo AI Agent in Priority Scoring can also help: "Find issues needing attention in project CORE — missing description category" returns a filtered list immediately.

Across multiple projects

The Portfolio view in Priority Scoring shows a health score for every project in your Jira instance side by side. Engineering managers and VPs with 4–8 active teams can see at a glance which projects are healthy and which need a refinement intervention — without opening each project individually. See more: Portfolio Backlog Health in Jira.

Frequently asked questions