Four questions people keep asking Jira dashboards, and the exact settings that answer each one. Every recipe takes under a minute and needs no JQL unless you want it.
"Who is carrying how much this sprint, in points rather than in tickets?"
Field Sum & Roll-up
| Setting | Value |
|---|---|
| Which issues | Your sprint filter, if you have one saved. Otherwise JQL I write myself with project = ABC AND sprint in openSprints(). |
| What to sum | Story points (or Story point estimate — whichever your instance calls it) |
| Group by | Assignee |
Unassigned work gets its own row rather than vanishing, which is usually the row worth looking at. If some issues have no estimate, the gadget says how many were counted as zero — a low total is never a mystery.
"How does the load split across teams — and how much is sitting outside all of them?"
Two Dimensional Filter Statistics
| Setting | Value |
|---|---|
| Which issues | A project, or a saved filter for the release you care about |
| Rows | Team |
| Columns | Status, or priority, or sprint — whatever the second question is |
| What to show in each cell | Issue count, or the sum of story points |
The built-in Two Dimensional Filter Statistics gadget cannot use the Team field at all — that limitation is what this gadget was built for. Issues with no team appear in an explicit (none) row instead of being dropped.
"We are three weeks in. Which epics are moving and which have not started?"
Epic Progress Bars
| Setting | Value |
|---|---|
| Which issues | The project or filter holding the work — pick one and subtasks are excluded for you |
| Measure progress by | Story points. Counting issues treats a one-point tweak and a thirteen-point rewrite as equals. |
| Order | Least complete first when you want the problem at the top; largest first when you want the weight. |
An issue counts as done when its status is in the Done category — the same rule Jira uses to strike through an issue key, so it matches what people already believe. Work with no epic is grouped under "No parent" rather than quietly excluded.
"Everything is 'in progress'. In progress doing what?"
Status Category Breakdown
| Setting | Value |
|---|---|
| Which issues | A sprint, a release, or a team's backlog |
| What to measure | Issue count, or story points |
The three stages are shown in workflow order rather than by size, each with its share of the total, and underneath each one the individual statuses that make it up — for example In Progress 3,200 · In Review 1,738. That second line is usually the answer: the work is not stuck in progress, it is waiting for review.
It should tell you why. The gadgets say when issues had no value in the field being summed, when an issue counts in several groups at once, when the result was cut at 20,000 issues, and when something became unreadable while the total was being calculated. If a number still does not add up, write to apps@probiusproiect.ro with the filter you used and what you expected — that is usually enough to reproduce it.