Templates & recipes
You rarely need to start from a blank dashboard. Insights and charts ships templates (a ready-made dashboard) and recipes (a single ready-made chart in the Add-widget gallery) for the questions teams ask most.
Templates
Create a new dashboard from any of these (left rail → New from template), or add their charts individually from the use-case gallery:
| Template | What it answers |
|---|---|
| Team overview | Issues by status / assignee / type / priority, fully cross-filterable. |
| Cycle time & flow | Cycle-time distribution, control chart with percentile lines, lead-time KPIs, created-per-month trend. |
| Time in status & WIP | Average time in status, current-status (WIP) aging, reopened issues. |
| SLA & aging | % within SLA, breached issues, SLA state by priority — against your target. |
| Flow history (CFD) | Open issues over time and a Cumulative Flow Diagram from change history. |
| Velocity & burndown | Committed-vs-completed velocity and sprint burndown from a Scrum board. |
| Epics & story points | Epic progress, % done, points by assignee/epic, epic → status drill, epic × status pivot. |
| Components & teams | Component × priority, workload by component/team. |
| Dependencies & blockers | % blocked, blocked vs. not, open blockers per issue, and the dependency matrix. |
Recipe catalog
Every standard Jira reporting use case maps to a concrete recipe. Find the chart in the Add-widget gallery, or build it with the chart · stat · dimension shown.
| # | Use case | How to build it |
|---|---|---|
| 1 | Issues by status / assignee / type | Team overview, or bar/pie · count · by status, assignee, or issue type. Click a bar to cross-filter. |
| 2 | Story points by assignee, stacked by status | Epics & story points → stacked · sum of points · assignee × status. |
| 3 | Unresolved by component & priority | Components & teams → grouped bars · count · component × priority; scope to unresolved. |
| 4 | Time in status per epic/sprint/assignee | Time in status & WIP → "Avg time in status"; cross-filter by epic/sprint/assignee. |
| 5 | Cycle / lead time distribution | Cycle time & flow → "By cycle-time bucket"; median / p85 KPIs. |
| 6 | Control chart (cycle-time scatter + percentiles) | Cycle time & flow → "Cycle-time control chart"; set the percentile in Options. |
| 7 | Created-age aging (unresolved by age) | Created-date variable, or JQL created <= -14d AND resolution = Unresolved; group by status. |
| 8 | WIP / status aging (time in current status) | Time in status & WIP → "WIP aging — current-status age". |
| 9 | SLA met % / breaches / time-to-resolution | SLA & aging → "% within SLA", "Breached issues", "SLA state by priority"; set the SLA target in Options. |
| 10 | Average resolution time + trend | KPI · avg · cycle-time days; Cycle time & flow → "Created per month — trend + 2-mo avg". |
| 11 | Created vs resolved over time | bar · count · created month (drill year→quarter→month→day); resolved via the activity calendar. |
| 12 | Open issues / unresolved-by-status over time | Flow history (CFD) → "Open issues over time". |
| 13 | Cumulative Flow Diagram | Flow history (CFD) → "Cumulative Flow Diagram" (stacked area). |
| 14 | Velocity (committed vs done per sprint) | Velocity & burndown → "Velocity — committed vs completed"; pick a Scrum board. |
| 15 | Sprint burndown / burnup | Velocity & burndown → "Sprint burndown — remaining vs ideal". |
| 16 | Epic progress / % done / time per epic | Epics & story points → "% Done" gauge, "Issues by epic", "Epic × Status" pivot. |
| 17 | Blocked / dependency aging (linked issues) | Dependencies & blockers → "% Blocked", "Open blockers per issue", and the Dependency matrix. |
| 18 | Cross-project / cross-team dashboard | Use a cross-project saved filter or custom JQL dataset; every widget applies. |
| 19 | Reopened issues / transition counts | Time in status & WIP → "Reopened issues". |
Next
- Derived metrics — the engine behind recipes 4–6, 8–10, 12–15, 19.
- Chart types and Dimensions & measures — to build any recipe by hand.