Use Case Templates
Ready-to-use dashboard templates with recommended gadget combinations, JQL, and configuration tips. Copy the JQL and gadget setups directly into your dashboard.
Template 1: Sprint Health Dashboard
Purpose: Daily standup and sprint review dashboard for Scrum teams Audience: Scrum Master, Development Team Update Frequency: Daily
Gadgets to Add (in order)
| Position | Gadget Type | Title |
|---|---|---|
| Row 1, Col 1 | Custom Charts - Pie | Sprint Status Overview |
| Row 1, Col 2 | Custom Charts - Tile | Sprint Completion % |
| Row 1, Col 3 | Custom Charts - Bar | Work by Assignee |
| Row 2, Full width | Dynamic Filter Controller | Sprint Filters |
| Row 3, Full width | Issue List | Sprint Backlog |
JQL for All Gadgets
sprint in openSprints() AND project = YOUR_PROJECT
Configuration Details
Pie Chart - Sprint Status Overview
- Source: JQL above
- Chart By: Status
- Colors: To Do = grey, In Progress = blue, Done = green, Blocked = red
Tile Chart - Sprint Completion %
- Source: JQL above
- Chart By: Custom JQL segments
- Segment 1 "Done":
status = Done - Segment 2 "Remaining":
status != Done
- Segment 1 "Done":
- Display: % format
Bar Chart - Work by Assignee
- Source: JQL above
- Chart By: Assignee
- Calculation: Count
- Add Average Line to show team average
Dynamic Filter Controller
- Source: JQL above
- Filter Fields: Assignee, Status, Priority, Sprint
- Add Tabs: "All Work" (no filter), "My Issues" (Assignee = currentUser()), "In Progress" (Status = In Progress)
Issue List - Sprint Backlog
- Source: JQL above
- Columns: Key, Summary, Status, Assignee, Story Points, Priority
- Sort: Status ascending
- Quick Filters: "Blocked" (
labels = blocked), "High Priority" (priority in (High, Highest)), "Unassigned" (assignee is EMPTY)
Template 2: Bug Tracking Dashboard
Purpose: Track all open bugs with priority, age, and assignment visibility Audience: QA Lead, Engineering Manager Update Frequency: Daily
Base JQL
issuetype = Bug AND resolution is EMPTY AND project = YOUR_PROJECT
Gadgets to Add
| Position | Gadget Type | Title |
|---|---|---|
| Row 1, Col 1 | Custom Charts - Pie | Bugs by Priority |
| Row 1, Col 2 | Custom Charts - Bar | Bugs by Assignee |
| Row 1, Col 3 | Custom Charts - Tile | Total Open Bugs |
| Row 2, Full width | Issue List | Open Bug List |
Configuration Details
Pie - Bugs by Priority
- Chart By: Priority
- Colors: Highest = dark red, High = orange, Medium = yellow, Low = light blue, Lowest = grey
Bar - Bugs by Assignee
- Chart By: Assignee
- Add Average Line
Tile - Total Open Bugs
- Source: JQL above
- Chart By: Status (show all statuses)
- Display: Count only, show total
Issue List - Open Bug List
- Columns: Key, Summary, Priority, Status, Assignee, Created, Component
- Sort: Priority descending
- Smart Labels: "Critical" (
priority = Highest), "Overdue" (duedate < now()) - Quick Filters: "Unassigned" (
assignee is EMPTY), "Critical" (priority = Highest), "My Bugs" (assignee = currentUser())
Template 3: Team Workload Dashboard
Purpose: Visualize work distribution and capacity across the team Audience: Engineering Manager, Team Lead Update Frequency: Weekly
Base JQL
project = YOUR_PROJECT AND resolution is EMPTY AND assignee is not EMPTY
Gadgets to Add
| Position | Gadget Type | Title |
|---|---|---|
| Row 1, Full width | Dynamic Filter Controller | Team Filters |
| Row 2, Col 1 | Custom Charts - Bar | Issues per Person |
| Row 2, Col 2 | Custom Charts - Bar | Story Points per Person |
| Row 2, Col 3 | Custom Charts - Pie | Status Overview |
| Row 3, Col 1 | Pivot Table | Assignee × Status Heatmap |
| Row 3, Col 2 | Time in Status | Where Work Slows Down |
| Row 4, Full width | Issue List | Team Work Queue |
Configuration Details
Bar - Issues per Person
- Chart By: Assignee
- Calculation: Count
- Add Average Line
- Add Goal Line at your team capacity limit (e.g., 10 issues per person)
Bar - Story Points per Person
- Chart By: Assignee
- Calculation: Sum of Story Points
- Add Average Line
Pie - Status Overview
- Chart By: Status
Issue List - Team Work Queue
- Columns: Assignee, Key, Summary, Status, Priority, Story Points, Due Date
- Sort: Assignee, then Priority
- Quick Filters: "Due This Week" (
duedate <= endOfWeek()), "High Priority" (priority in (High, Highest))
Template 4: Release Readiness Dashboard
Purpose: Track release scope completion and outstanding blockers Audience: Release Manager, Product Owner Update Frequency: Daily during release period
Base JQL (replace v2.0 with your fix version)
fixVersion = "v2.0" AND project = YOUR_PROJECT
Gadgets to Add
| Position | Gadget Type | Title |
|---|---|---|
| Row 1, Col 1 | Custom Charts - Pie | Release Completion |
| Row 1, Col 2 | Custom Charts - Tile | Critical Blockers |
| Row 1, Col 3 | Custom Charts - Line | Resolution Velocity |
| Row 2, Col 1 | Cumulative Flow Diagram | Flow Health Across the Release |
| Row 2, Col 2 | Work Breakdown Structure | Epic Breakdown and Blockers |
| Row 3, Full width | Issue List | Outstanding Items |
Configuration Details
Pie - Release Completion
- Chart By: Custom JQL segments
- "Done":
fixVersion = "v2.0" AND resolution is not EMPTY - "Remaining":
fixVersion = "v2.0" AND resolution is EMPTY
- "Done":
- Colors: Done = green, Remaining = orange
Tile - Critical Blockers
- Source:
fixVersion = "v2.0" AND priority = Highest AND resolution is EMPTY - Display: Count only (large number format)
- If count > 0, this number needs attention
Line - Resolution Velocity
- Source:
fixVersion = "v2.0" AND resolved >= -30d - Chart By: Resolved (by Day)
- Date Grouping: Days
- Add Trend Line to see if velocity is increasing
Issue List - Outstanding Items
- Source:
fixVersion = "v2.0" AND resolution is EMPTY - Columns: Key, Summary, Priority, Status, Assignee, Component
- Sort: Priority descending
- Smart Labels: "Blocker" (
labels = blocker), "Needs Review" (status = "In Review")
Template 5: Executive Summary Dashboard
Purpose: High-level KPI view for leadership Audience: Director, VP, C-Suite Update Frequency: Weekly
Gadgets to Add
| Position | Gadget Type | Title |
|---|---|---|
| Row 1, 4 tiles | Custom Charts - Tile | Open Issues, Critical Bugs, Resolved This Month, Active Team Members |
| Row 2, Col 1 | Custom Charts - Bar | Monthly Issue Trend |
| Row 2, Col 2 | Custom Charts - Stacked Bar | Project Health |
| Row 3, Col 1 | Issue Filter Formula | Delivery KPIs as gauges |
| Row 3, Col 2 | Kanban Velocity | Throughput and Backlog ETA |
JQL for Each Tile
| Tile | JQL |
|---|---|
| Open Issues | project in (X, Y, Z) AND resolution is EMPTY |
| Critical Bugs | issuetype = Bug AND priority = Highest AND resolution is EMPTY |
| Resolved This Month | resolved >= startOfMonth() AND project in (X, Y, Z) |
Tips for Executive Dashboards
- Use the Description tab on each gadget to add plain-language context below the chart
- Rename Jira status values to business language in segment labels (e.g., "In Progress" → "Active")
- Export to PDF monthly for board packs
- Set gadget titles to be stakeholder-friendly (avoid Jira jargon like "JQL" or "Assignee")
Template 6: Delivery Metrics Dashboard
Purpose: Measure how fast work actually moves, and how predictable that is Audience: Engineering Manager, Delivery Lead, Agile Coach Update Frequency: Reviewed monthly or per sprint
Data Source
Use a Board source so every gadget is scoped to the same team without maintaining parallel JQL.
Gadgets to Add
| Position | Gadget Type | Title |
|---|---|---|
| Row 1, Col 1 | Control Chart | Cycle Time per Item |
| Row 1, Col 2 | Histogram Chart | Cycle Time Distribution |
| Row 2, Col 1 | Cycle Time Trend | Are We Getting Faster? |
| Row 2, Col 2 | WIP Run Chart | Work in Progress |
| Row 3, Full width | WIP Aging Charts | What Is Old Right Now |
Configuration Details
Control Chart - Cycle Time per Item
- Metric: Cycle Time, starts when the issue enters In Progress, ends when it enters Done
- Date Interval: Last 90 days
- Percentile lines: 50 and 85
- Turn on the rolling average to see drift over the period
Histogram Chart - Cycle Time Distribution
- Same cycle definition as the Control Chart
- Date Interval: Last 364 days (a distribution needs volume - below about 30 items the shape is noise)
- Split: 10 equal intervals to start, then switch to custom thresholds matching your SLA tiers
Cycle Time Trend - Are We Getting Faster?
- Interval: Board Sprints, so each bar is a sprint the team remembers
- Intervals to display: 12
- Trendline: Linear
- Leave "include the current interval" off - a partial interval reads misleadingly low
WIP Run Chart - Work in Progress
- WIP rule: status category "In Progress"
- Calculate by: Work Item Count
- Set a max limit slightly below your observed average, then watch whether cycle time improves
WIP Aging Charts - What Is Old Right Now
- Age method: Time since last entry in current status
- Threshold line at your SLA, percentile line at 85
Tips for Delivery Metrics Dashboards
- Use the same cycle definition across Control Chart, Histogram, and Cycle Time Trend, and write it into each Description tab
- Quote the 85th percentile, not the average, when someone asks how long something will take
- Fix WIP before trying to fix cycle time - the run chart usually explains the control chart
Template 7: Standup Wallboard
Purpose: A board and sprint view that runs unattended on a screen in the team area Audience: The whole team, at standup Update Frequency: Auto-refreshing
Data Source
A Board source, scoped to the active sprint.
Gadgets to Add
| Position | Gadget Type | Title |
|---|---|---|
| Row 1, Full width | Team Wallboard | Today's Board |
| Row 2, Col 1 | Sprint Burndown & Burnup | Sprint Progress |
| Row 2, Col 2 | WIP Aging Charts | Needs a Conversation |
| Row 3, Col 1 | Countdown | Days to Sprint End |
| Row 3, Col 2 | Regional Clock | Team Time Zones |
Configuration Details
Team Wallboard - Today's Board
- Source: Board, active sprint
- Grouping: Board columns
- Quick filters: any of the board's own Jira Quick Filters (optional)
- Compact cards on, auto-refresh on, options menu off
- Swimlanes: by assignee for workload, or none for a small team
Sprint Burndown & Burnup - Sprint Progress
- Sprint: Latest sprint (auto) so it follows the team across sprint boundaries
- Series: Remaining plus Ideal Burndown for the cleanest standup read
- Weekend mode: non-working
WIP Aging Charts - Needs a Conversation
- Threshold line at your team's SLA
- Any dot past the line gets discussed
Countdown - Days to Sprint End
- Target: the sprint end date
- Time format: Days, Hours
- "Don't count weekends" on if the remaining work only happens on business days
Regional Clock - Team Time Zones
- One gadget per office; add as many as you have locations
Tips for Wallboards
- Turn the options menu off on every gadget so a passer-by cannot reconfigure the display
- Auto-refresh belongs here, but turn it off on dashboards used only in scheduled meetings
- Keep the board to one screen - if it scrolls, it stops being glanceable