Use Cases
Dashboard Widgets
Team Performance
Purpose: Monitor team activity, engagement levels, and identify work that needs immediate attention. These queries are perfect for daily standup dashboards, team lead reviews, and identifying productivity patterns.
# Issues with recent activity
# Use for: Daily standup dashboards, weekly team reviews, activity heatmaps
# Why it matters: Shows which issues have active discussion or updates, indicating current focus areas
# Dashboard widget: Use as a pie chart showing "Active vs Inactive" work
commentsCount > 0 AND updated >= startOfWeek()
# High-engagement issues
# Use for: Executive dashboards, stakeholder reporting, critical issue identification
# Why it matters: High watcher/voter counts indicate business-critical or controversial issues
# Dashboard widget: Create a "Hot Issues" list widget with issue keys and titles
watchersCount > 5 OR votersCount > 3
# Issues needing attention
# Use for: Team health dashboards, work abandonment alerts, process compliance monitoring
# Why it matters: Silent old issues often indicate blocked work, unclear requirements, or forgotten tasks
# Dashboard widget: Red alert list for immediate team action
commentsCount = 0 AND created <= -7d
Recommended Dashboard Layout:
Top row: Activity gauge (percentage of issues with recent activity)
Middle row: Hot issues table with links to actual issues
Bottom row: Alert list of silent issues requiring attention
Epic Management
Purpose: Track epic delivery health, identify scope creep, and monitor cross-epic dependencies. Essential for release planning, portfolio management, and agile scaling.
# Epic progress tracking
# Use for: Release dashboards, epic burndown tracking, delivery health monitoring
# Why it matters: Shows completed work that belongs to active epics - indicates scope completion
# Dashboard widget: Burndown chart showing "Completed Work in Active Epics"
issue in childrenOfEpicsInQuery("status != Done") AND status = "Done"
# Find epics with blocked children
# Use for: Risk management dashboards, escalation tracking, dependency monitoring
# Why it matters: Blocked work under epics indicates delivery risks and need for management intervention
# Dashboard widget: Risk heatmap showing epics by number of blocked children
issue in epicsOfChildrenInQuery("status = Blocked")
# Epic children status distribution
# Use for: Epic-level burndown charts, scope tracking, completion forecasting
# Why it matters: Provides real-time view of work remaining under each epic for planning
# Dashboard widget: Stacked bar chart showing status distribution across epic children
isEpicChild = "true" AND parentStatus != "Done"
Recommended Dashboard Layout:
Epic health scorecard with completion percentages
Risk matrix showing epics with blocked vs flowing work
Timeline view of epic completion forecasts based on current velocity
Process Improvement
Workflow Analysis
Purpose: Identify systemic bottlenecks, process inefficiencies, and workflow violations. Critical for continuous improvement, process optimization, and team performance enhancement.
# Find bottlenecks
# Use for: Process improvement retrospectives, workflow optimization, capacity planning
# Why it matters: Work stuck in status for 2+ weeks indicates process bottlenecks or resource constraints
# Dashboard widget: Bottleneck heatmap showing issues by status and time stuck
# Action items: Review with team leads, identify root causes, implement process changes
issue in workflowFunctions("timeInStatus>14days")
# Identify quick fixes
# Use for: Complexity analysis, process efficiency measurement, skill gap identification
# Why it matters: Same-day resolutions indicate either very simple work or excellent preparation
# Dashboard widget: Quick win percentage gauge and trend over time
# Follow-up: Analyze patterns to replicate success factors in other work
issue in dateCompareIgnoreTime("resolved = created")
# Find process violations
# Use for: Data quality audits, process compliance monitoring, system health checks
# Why it matters: Issues resolved before creation indicate data integrity problems or process errors
# Dashboard widget: Data quality alert count with drill-down capability
# Action items: Investigate data import processes, user training needs, system bugs
issue in dateCompare("resolved < created")
Advanced Analysis:
Combine with project and team filters to identify specific bottleneck sources
Track bottleneck trends over time to measure process improvement effectiveness
Use with assignee data to identify individual coaching opportunities
Quality Assurance
Purpose: Monitor documentation standards, communication quality, and Definition of Done compliance. Essential for maintaining delivery quality and team knowledge sharing.
# Issues missing documentation
# Use for: Definition of Done compliance dashboards, quality gate monitoring, technical debt tracking
# Why it matters: Completed stories without attachments may lack proper documentation or acceptance criteria
# Dashboard widget: Compliance percentage gauge with trend over time
# Action items: Implement documentation requirements, update Definition of Done, team training
attachmentsCount = 0 AND type = "Story" AND status = "Done"
# Over-discussed issues
# Use for: Complexity identification, architectural review triggers, scope clarity assessment
# Why it matters: 20+ comments often indicate unclear requirements, technical complexity, or scope creep
# Dashboard widget: Complexity heatmap with issue drill-down
# Follow-up: Schedule architectural review, break into smaller stories, clarify requirements
commentsCount > 20
# Under-documented issues
# Use for: Knowledge sharing assessment, onboarding readiness, maintenance risk evaluation
# Why it matters: Old issues without discussion lack context for future maintenance or similar work
# Dashboard widget: Knowledge gap alert with severity levels
# Action items: Encourage documentation, implement knowledge sharing practices
commentsCount < 2 AND created <= -30d
Quality Metrics Dashboard:
Documentation compliance rate trending over sprints
Communication quality indicators (average comments per story type)
Knowledge sharing effectiveness (percentage of well-documented issues)
Release Management
Version Tracking
Purpose: Monitor release health, identify schedule risks, and ensure version compliance across all work streams. Critical for delivery predictability and stakeholder communication.
# Overdue releases
# Use for: Release risk dashboards, schedule impact assessment, stakeholder communication
# Why it matters: Overdue versions indicate scope creep, estimation issues, or external dependencies
# Dashboard widget: Release health scorecard with risk levels (red/yellow/green)
# Action items: Scope review, timeline adjustment, dependency resolution, stakeholder updates
"Has Overdue Versions" = "true"
# Released version impact
# Use for: Post-release analysis, delivery metrics, business value assessment
# Why it matters: Shows actual delivered scope vs planned scope for completed releases
# Dashboard widget: Delivery timeline showing released vs planned features
# Follow-up: Retrospective on delivery accuracy, process improvement opportunities
"Fix Versions Released" > 0
# Upcoming release work
# Use for: Sprint planning, resource allocation, delivery forecasting
# Why it matters: Identifies work committed to near-term releases for prioritization and planning
# Dashboard widget: Upcoming releases workload distribution with capacity indicators
# Planning use: Capacity planning, dependency identification, timeline validation
nextReleaseDate <= endOfMonth()
Release Command Center Dashboard:
Current release burn-up/burn-down charts
Risk indicators for upcoming releases
Historical delivery accuracy trends
Cross-team dependency tracking
Dependency Management
Purpose: Track cross-team dependencies, external blockers, and integration points. Essential for coordination at scale and minimizing delivery risks.
# External dependencies
# Use for: Cross-team coordination dashboards, dependency mapping, integration planning
# Why it matters: Work linking to other projects indicates coordination needs and potential blockers
# Dashboard widget: Dependency network diagram showing project interconnections
# Action items: Schedule coordination meetings, establish communication channels, track delivery commitments
linkedProject !~ currentProject()
# Blocking relationships
# Use for: Daily standup focus, impediment tracking, escalation management
# Why it matters: Active blockers directly impact delivery timeline and require immediate attention
# Dashboard widget: Blocker burn-down chart with aging indicators
# Daily process: Review in standups, assign owners for resolution, escalate as needed
linksType ~ "blocks" AND linksStatus != "Done"
# Cross-project work
# Use for: Portfolio management, resource allocation, scope boundary management
# Why it matters: Epic work spanning projects indicates complex initiatives requiring coordination
# Dashboard widget: Cross-project impact matrix showing scope distribution
# Portfolio use: Resource planning, timeline coordination, scope management
issue in childrenOfEpicsInQuery("project != MYPROJECT")
Dependency Command Center:
Live blocker count with aging analysis
Cross-team dependency heat map
Integration timeline with milestone tracking
Escalation queue for high-impact blockers
Advanced Scenarios
Executive Reporting
Purpose: Provide leadership with high-level insights into delivery health, team performance, and strategic initiative progress.
# Strategic initiative health
# Combine epic progress with engagement metrics for leadership visibility
issue in epicsOfChildrenInQuery("labels = strategic") AND (votersCount > 3 OR watchersCount > 5)
# Cross-functional collaboration indicators
# Show work requiring multiple team coordination
linkedProject !~ currentProject() AND commentsCount > 5 AND worklogsCount > 0
# Innovation pipeline
# Track experimental or research work patterns
attachmentsCount > 2 AND commentsCount > 10 AND type in ("Research", "Spike", "Investigation")
Team Health Monitoring
Purpose: Identify team dynamics, workload distribution, and potential burnout indicators through work patterns.
# Collaborative work patterns
# Issues with high engagement indicate good team collaboration
commentsCount > 5 AND worklogsCount > 0 AND watchersCount > 2
# Isolation indicators
# Work with low engagement may indicate team isolation or unclear scope
commentsCount <= 1 AND watchersCount = 0 AND created <= -14d
# Knowledge sharing effectiveness
# Well-documented completed work indicates good knowledge transfer
status = "Done" AND attachmentsCount > 0 AND commentsCount between 3 and 10