Use Cases

Common Use Cases

Real-world examples of how teams use Dashboard Templates, Charts, Graphs & Reports for Jira to visualize their work, track progress, and make faster decisions.


1. Sprint Dashboard

Who: Scrum Masters, Agile Coaches, Development Teams When: Sprint planning, daily standups, sprint reviews

What It Shows

A complete view of the current sprint - what's done, what's in progress, what's blocked, and how much work remains.

GadgetConfigurationPurpose
Custom Charts (Pie)Data: Current Sprint JQL sprint in openSprints() - Chart By: StatusSprint status distribution at a glance
Custom Charts (Bar)Data: Same sprint - Chart By: Assignee - Calculation: CountWork distribution across team members
Custom Charts (Tile)Data: Sprint JQL - Chart By: Custom JQL segments (Done vs Total)Story point completion percentage
Issue ListData: Sprint JQL - Columns: Key, Summary, Status, Assignee, Story PointsFull sprint backlog with click-through to issues
Dynamic Filter ControllerData: Sprint JQL - Fields: Assignee, Status, PriorityLet team members filter by their own name

Configuration Tips

  • Use sprint in openSprints() as your base JQL to always show the current sprint
  • Add a Goal Line to the bar chart at your sprint velocity target (e.g., 40 story points)
  • Connect all gadgets to the Dynamic Filter Controller so the whole dashboard updates when a team member filters by their name
  • Add Smart Labels to the Issue List for "Blocked" (labels = blocked) and "High Priority" (priority in (High, Highest))

2. Bug Tracking Dashboard

Who: QA Leads, Engineering Managers, Release Managers When: Active development sprints, pre-release periods, production incident tracking

What It Shows

A focused view of all open bugs - by severity, age, assignment status, and component.

GadgetConfigurationPurpose
Custom Charts (Pie)Data: issuetype = Bug AND resolution is EMPTY - Chart By: PriorityBug severity distribution
Custom Charts (Bar)Data: Open bugs - Chart By: AssigneeBug ownership per developer
Custom Charts (Stacked Bar)Data: Open bugs - Chart By: Component - Group By: PriorityPriority mix per component
Custom Charts (Line)Data: issuetype = Bug AND created >= -90d - Chart By: Created (by Week)Bug creation trend over 90 days
Issue ListData: Open bugs - Columns: Key, Summary, Priority, Status, Assignee, Created, ComponentFull bug list sortable by priority

Configuration Tips

  • Set Chart By to Priority for the pie chart and map colors: Highest = red, High = orange, Medium = yellow
  • Add a Quick Filter to the Issue List: "Unassigned" (assignee is EMPTY) to quickly spot untriaged bugs
  • Use the Stacked Bar chart to identify which components have the highest proportion of critical bugs
  • Add a Trend Line to the line chart to see if bug volume is increasing or decreasing

3. Team Workload Dashboard

Who: Engineering Managers, Team Leads, Project Managers When: Weekly team reviews, capacity planning, identifying overloaded team members

What It Shows

Who has what - a clear picture of work distribution across the team to spot imbalances before they become problems.

GadgetConfigurationPurpose
Custom Charts (Bar)Data: project = X AND resolution is EMPTY - Chart By: AssigneeIssue count per team member
Custom Charts (Grouped Bar)Data: Same - Chart By: Assignee - Group By: StatusWork stage breakdown per person
Custom Charts (Stacked Bar)Data: Same - Chart By: Assignee - Group By: PriorityPriority distribution per person
Custom Charts (Bar)Data: Same - Chart By: Assignee - Calculation: Sum of Story PointsStory point load per person
Issue ListData: Same - Columns: Assignee, Key, Summary, Status, Priority, Due DateFull team work queue

Configuration Tips

  • Add an Average Line to the issue count bar chart - immediately shows who is above/below team average
  • Use Sum of Story Points calculation to compare actual work complexity, not just ticket count
  • Add a Quick Filter "Due This Week" (duedate >= startOfWeek() AND duedate <= endOfWeek()) to the Issue List
  • Connect all gadgets to a Dynamic Filter Controller with an Assignee field - managers can click a name to see that person's view

4. Release Readiness Dashboard

Who: Release Managers, Product Owners, Engineering Managers When: Pre-release week, release gate reviews, stakeholder sign-off meetings

What It Shows

Everything needed to decide if the release is ready - open blockers, remaining work by component, fix version status, and resolved vs unresolved ratio.

GadgetConfigurationPurpose
Custom Charts (Pie)Data: fixVersion = "v2.0" - Chart By: Custom JQL (Done vs Not Done)Overall release completion percentage
Custom Charts (Stacked Bar)Data: Fix version JQL - Chart By: Component - Group By: StatusCompletion by component
Custom Charts (Tile)Data: fixVersion = "v2.0" AND priority = Highest AND resolution is EMPTY - Chart By: StatusCritical open blockers count
Issue ListData: fixVersion = "v2.0" AND resolution is EMPTY AND priority in (Highest, High) - Columns: Key, Summary, Priority, Status, AssigneeHigh-priority outstanding items
Custom Charts (Line)Data: Fix version JQL - Chart By: Resolved (by Day)Resolution velocity trend

Configuration Tips

  • Create JQL segments for the pie chart: "Done" (resolution is not EMPTY) and "Remaining" (resolution is EMPTY)
  • Set a Goal Line on the line chart at your target daily resolution rate
  • Use Smart Labels in the Issue List for "Blocker" (labels = blocker) and "Needs QA" (status = "Ready for QA")
  • Share this dashboard with stakeholders using Jira's dashboard sharing - they can view without edit access

5. Executive KPI Dashboard

Who: VPs, Directors, C-Suite, Senior Stakeholders When: Weekly/monthly reviews, board meetings, OKR check-ins

What It Shows

High-level metrics without noise - the numbers that matter to leadership, presented cleanly without Jira-specific terminology.

GadgetConfigurationPurpose
Custom Charts (Tile)Data: project in (X, Y, Z) AND resolution is EMPTYTotal open issues across all projects
Custom Charts (Tile)Data: issuetype = Bug AND priority = Highest AND resolution is EMPTYCritical open bugs
Custom Charts (Tile)Data: sprint in openSprints() AND resolution is not EMPTYIssues resolved this sprint
Custom Charts (Bar)Data: created >= -12w - Chart By: Created (by Month)Issue creation trend (last 3 months)
Custom Charts (Stacked Bar)Data: Multi-project - Chart By: Project - Group By: StatusCross-project health overview

Configuration Tips

  • Use Tile charts for the top row - one number per tile, large and clear
  • Rename segment labels to business-friendly terms (e.g., rename "In Progress" to "Active Work")
  • Set the title of each gadget clearly (e.g., "Open Critical Bugs" not "Priority = Highest, resolution is EMPTY")
  • Use the Description tab to add context below charts (e.g., "As of last refresh - click Refresh to update")
  • Export the dashboard view as PDF for board packs and email updates

6. Support & Service Desk Dashboard

Who: Support Leads, Customer Success Managers, Operations Teams When: Daily team huddles, SLA review meetings, capacity planning

GadgetConfigurationPurpose
Custom Charts (Funnel)Data: All open support tickets - Chart By: Status (ordered by workflow)Ticket pipeline visualization
Custom Charts (Bar)Data: created >= -7d - Chart By: AssigneeNew tickets per agent this week
Issue ListData: Open high-priority tickets - Smart Labels: Overdue, EscalatedTickets needing immediate attention

Configuration Tips

  • Order funnel segments to match your support workflow (e.g., New → Triaged → In Progress → Pending Customer → Resolved)
  • Add a Smart Label "Overdue" using duedate < now() AND resolution is EMPTY with a red badge
  • Add Quick Filters: "My Tickets" (assignee = currentUser()), "Unassigned" (assignee is EMPTY)