Use Cases

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)

PositionGadget TypeTitle
Row 1, Col 1Custom Charts - PieSprint Status Overview
Row 1, Col 2Custom Charts - TileSprint Completion %
Row 1, Col 3Custom Charts - BarWork by Assignee
Row 2, Full widthDynamic Filter ControllerSprint Filters
Row 3, Full widthIssue ListSprint 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
  • 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

PositionGadget TypeTitle
Row 1, Col 1Custom Charts - PieBugs by Priority
Row 1, Col 2Custom Charts - BarBugs by Assignee
Row 1, Col 3Custom Charts - TileTotal Open Bugs
Row 2, Full widthIssue ListOpen 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

PositionGadget TypeTitle
Row 1, Full widthDynamic Filter ControllerTeam Filters
Row 2, Col 1Custom Charts - BarIssues per Person
Row 2, Col 2Custom Charts - BarStory Points per Person
Row 2, Col 3Custom Charts - PieStatus Overview
Row 3, Full widthIssue ListTeam 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

PositionGadget TypeTitle
Row 1, Col 1Custom Charts - PieRelease Completion
Row 1, Col 2Custom Charts - TileCritical Blockers
Row 1, Col 3Custom Charts - LineResolution Velocity
Row 2, Full widthIssue ListOutstanding 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
  • 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

PositionGadget TypeTitle
Row 1, 4 tilesCustom Charts - TileOpen Issues, Critical Bugs, Resolved This Month, Active Team Members
Row 2, Col 1Custom Charts - BarMonthly Issue Trend
Row 2, Col 2Custom Charts - Stacked BarProject Health

JQL for Each Tile

TileJQL
Open Issuesproject in (X, Y, Z) AND resolution is EMPTY
Critical Bugsissuetype = Bug AND priority = Highest AND resolution is EMPTY
Resolved This Monthresolved >= 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")
Previous
Common Use Cases
Next
FAQ