Dashboard presets

The QA Metrics page shows all six metrics of one team on a single page. A role preset only changes their order; values, counting rules, access and collection stay the same.

The dashboard

The header shows the team name, its board and the chosen sprint. From left to right it holds:

a team list, when more than one team exists;
the sprint list (screen readers announce it as “As of sprint:”), starting with Choose a closed sprint;
the Team and admin tools menu (gear) with Team settings, Start or resume setup and Administration. Team settings appears when you can see a board; Administration only for users with the Administer Jira global permission.

Below the header come six tiles, one per metric, each with a headline number, a small chart and one line of context. Selecting a tile scrolls to its section.

Then follow six sections with the default titles Sprint commitment, Epic progress, Defect leakage, Reopen rate, Test pyramid and Requirement coverage. Each section has a Count / Percent switch and ends with a How we count caption. Requirement coverage also has By sprint / By epic.

Selecting a section title opens the side panel … details, for example Defect leakage details, with the explanation, lists and older views. The sliders button next to the switch, labelled … settings for screen readers, opens the side panel … settings.

A page address ending in /metrics/<metric> opens that metric’s details panel, and one ending in /configure/<metric> its settings panel. Dashboard gadgets link to the details panel.

The footer says which sprint the numbers belong to, for example “Numbers are for Sprint 14 as saved when it closed.” Unknown results are never counted as zero.

Role presets

The header offers three role presets:

QA lead: “QA lead puts coverage and defects first.”
Scrum master: “Scrum master puts the sprint commitment first.” This is the default for a new team.
Manager: “Manager puts epics and delivery first.”

Selecting a preset saves it for the team at once; the header shows “Saving for this team…” while it saves. Anyone who can see that team’s board can change the shared choice, and the latest save is used.

If the save cannot be confirmed, the header says “The save could not be confirmed. Reload to check the saved order.” Reload before trying again.

A preset does not combine the metrics into an overall score. Existing Jira dashboard gadgets keep their own configuration.

Arrange metrics

Arrange metrics lets you set your own order. Drag a tile, or use ← Earlier, Later → or Pin first on a tile; the sections below follow at once. The order is saved for the team.

While you arrange, the preset group shows Custom. Reset to role order returns to the order of the selected preset, and Done closes arranging.

Title and display defaults

Open a metric’s … settings panel. It starts with Make this metric fit your team, then Title on the dashboard, Display defaults and Counting rules and sources.

Title on the dashboard takes up to 80 characters; leave it blank to use the default title. Save it with Save title.

Display defaults are shared by the team and saved with Save display defaults:

Default chart unit: Standard for each view, Count or Percent. A section starts from this unit.
Default view: Standard view or one of the metric’s views. It applies when the metric’s details panel opens. For the test pyramid there is no view choice: “The pyramid workspace shows saved results, Live and history together.”
Animate charts. Your device’s reduced motion setting always takes precedence.

You can still change the unit or view while exploring. Headline formulas and views with fixed units keep their meaning. Gadgets and setup examples keep their own settings.

If the saved defaults cannot be confirmed, the panel asks you to reload before editing, and the metric shows “Saved display defaults are unavailable. Using standard view settings.” Changing display defaults does not collect reports, change counting rules or select an epic for you.