What is Dashboard Templates, Charts, Graphs & Reports for Jira?
Dashboard Templates, Charts, Graphs & Reports for Jira is a reporting app that helps you see your Jira data in a clear, visual way.
Core Value Proposition
- Make charts and graphs from your Jira issues with no coding required - 10 chart types, from a simple pie to a two-dimensional matrix
- Build tables, issue lists, and pivot summaries with configurable columns, smart labels, and quick filters
- Measure delivery speed and flow from your issue history - cycle time, lead time, time in status, work-in-progress, and where work actually slows down
- Track sprints and forecast delivery with burndown, burnup, velocity, and a board-based backlog ETA
- See how work breaks down as an Epic-to-sub-task tree, a linked-issue map, or a wallboard of cards readable from across the room
- Compute KPIs from up to nine independent queries at once and show them as numbers, gauges, or star ratings
- Drive the whole dashboard from one shared filter bar, so viewers slice every gadget at once without editing anything
- Export everything as PNG, PDF, or CSV for stakeholders and reporting
All of this is done inside Jira, using your existing projects, boards, filters, and JQL.
Product Introduction Video
Nineteen Integrated Gadgets
| Gadget | What It Does |
|---|---|
| Custom Charts | Create 10 types of charts from Jira issues, including pie, bar, line, table, funnel, tile and 2D charts. |
| Issue List | Display Jira issues in a configurable table with custom columns, smart labels, and quick filters |
| Dynamic Filter Controller | Create a shared filter bar that controls multiple charts and lists simultaneously |
| Time in Status | Analyze exactly how long issues spend in each workflow status using changelog-based calculations |
| Pivot Table | Summarize issues in a cross-tabulation with flexible row/column grouping and 9 display types |
| Cumulative Flow Diagram | Visualize work distribution across workflow stages over time as a stacked area chart |
| WIP Aging Charts | Scatter plot showing how long work-in-progress items have been active - spot stalled work instantly |
| Control Chart | Cycle time and lead time of completed work as a scatter chart, with average, rolling average, threshold, and percentile lines |
| Histogram Chart | Frequency distribution of cycle and lead time - shows the shape of your delivery and the size of the slow tail |
| Cycle Time Trend | One bar per interval showing average cycle time over weeks, months, or sprints, with an optional trendline |
| WIP Run Chart | Work-in-progress over time as a line chart, with WIP limits and breach highlighting |
| Sprint Burndown & Burnup | Sprint progress day by day - remaining, burned, scope, and ideal lines for both burndown and burnup |
| Release Burndown & Burnup | Release progress over custom dates, a project release, or a sprint - with end-date and scope forecasts and milestones |
| Team Wallboard | Work items as cards grouped into board columns or status categories, with swimlanes and auto-refresh |
| Issue Filter Formula | KPIs built from up to nine independently-scoped aggregations combined with math formulas; number, gauge, star, or card display |
| Work Breakdown Structure | Expandable tree view of a work-item hierarchy (Epic → Story/Task → Sub-task) or linked-issue breakdown |
| Kanban Velocity | Completed work per interval as a bar chart with a rolling Average Velocity line, plus a board-based backlog forecast |
| Regional Clock | Current time and date for a chosen region and time zone - no Jira data required |
| Countdown | Remaining time until an upcoming event, milestone, or deadline, optionally counting only workdays |
Choosing between the flow metrics gadgets
Six gadgets measure delivery speed. They all read the same issue history, but they answer different questions:
| Question | Gadget |
|---|---|
| How long does each finished item take, and how consistent is that? | Control Chart |
| What does the spread look like - is there a long slow tail? | Histogram Chart |
| Are we getting faster or slower over time? | Cycle Time Trend |
| How much work is open at once, and are we over our limits? | WIP Run Chart |
| Which open items are old right now? | WIP Aging Charts |
| Which step in the workflow is actually the slow one? | Time in Status |
How Gadgets Get Their Data
Every gadget that reads Jira data is scoped the same way, so you only learn this once:
| Source | Use When |
|---|---|
| Projects | One or more whole Jira projects |
| Board | A Jira Software board - its own filter and column layout are picked up automatically |
| Saved Filter | A Jira filter your team already maintains |
| Custom JQL | You need precise control over exactly which issues are included |
| Dynamic Filter Controller | Viewers should be able to re-scope the gadget themselves from a shared filter bar |
Three exceptions: Sprint Burndown & Burnup is board-scoped by design, Release Burndown & Burnup also offers Epics and Portfolio-level items, and Regional Clock and Countdown read no Jira data at all.
Who Is It For?
- Scrum Masters who need sprint health charts, burndown views, and daily standup dashboards
- Product Owners who need backlog health, release readiness, and priority breakdowns
- Engineering Managers who need team workload charts and bug trend analysis
- Executives who need high-level KPI dashboards without digging into Jira
- QA Leads who need defect tracking and quality metrics at a glance
Benefits & Outcomes
Better Visibility
- See your Jira data at a glance with visual charts
- Spot trends, bottlenecks, and issues before they become problems
- Share insights with stakeholders who don't use Jira
Save Time
- Build reports in minutes, not hours
- No coding or external tools required
- Reuse configurations across dashboards with Import/Export
Make Better Decisions
- Data-driven insights for sprint planning
- Track progress against goals with reference lines
- Compare performance across teams, sprints, or time periods
Platform
Jira Cloud only. Built on Atlassian Forge, which means it runs inside Atlassian's own infrastructure - no external servers, no Jira data leaving your site, and nothing for you to host or maintain.