Dashboard gadgets for teams who want real Jira data, not a stripped-down summary — rendered fast and computed entirely inside Atlassian. Chart any saved JQL, track Agile flow metrics straight from the issue changelog, and get changelog-accurate Time in Status without waiting on an external service to respond.
Dashboards for Jira is a native gadget library for the Jira dashboard — not a separate reporting app. Each gadget is configured in standard gadget edit mode and computed live from your JQL. Chart library: bar, column, stacked, pie/donut, line, area, and pivot/two-dimensional tables, each driven by a saved filter or JQL. Agile flow, computed in Forge from the issue changelog and the Agile v1 API: burndown, burnup, cumulative flow diagram (CFD), velocity, and control chart. Time in Status: per-issue and aggregate time-in-status, cycle time, and lead time derived from the changelog, with working-calendar (business hours) support so off-hours don't count toward the total. Config panel: a React-based settings screen with a saved JQL/filter picker, grouping and segmentation field, date range, and color theming. Settings persist per gadget via Forge storage. Live refresh against Jira REST v3 and Agile v1, backed by a short-TTL result cache so gadgets render fast instead of re-querying on every dashboard load. Export: send a single chart to PNG or PDF, or export the underlying data set to CSV. Runs on Atlassian: 100% in-platform computation with zero external egress — every chart and metric stays inside your Atlassian cloud, which is what a security-reviewed enterprise buyer is checking for.
A short-TTL Forge KVS cache and metrics-instrumented gadgets mean charts paint on first load instead of stalling while data comes in — no more waiting for a dashboard to catch up before a standup or review.
Every chart, the Time in Status changelog crunching, and the result cache run inside Atlassian's Forge runtime — there's no external server, API key, or data pipeline to explain to your security team, and the Runs on Atlassian badge documents that for procurement.
Time in Status, cycle time, and lead time are calculated straight from the issue changelog, with optional working-calendar support, so a weekend doesn't inflate a 3-day 'In Progress' stint — the CFD, control chart, and velocity gadgets reuse the same data, so the numbers agree with each other.
Does any of my Jira data leave Atlassian?
No. Every chart, the Time in Status changelog crunching, and the result cache run inside Forge on Atlassian's infrastructure — there's no external server or API endpoint for your data to pass through.
How is Time in Status different from just reading status change history?
It aggregates the changelog into per-issue and per-group time-in-status, cycle time, and lead time, with an optional working-calendar setting so nights and weekends don't count toward the total.
Will the gadgets work with my saved filters and JQL?
Yes — each gadget's config panel has a saved filter/JQL picker plus grouping and date-range controls, and the settings persist per gadget via Forge storage.
Can I get data out of a gadget, not just view it on a dashboard?
Yes, each chart can be exported to PNG or PDF, and its underlying data set can be exported to CSV.
What's the pricing model?
Pricing model: Free up to 10 users, per-user pricing from 11 users, billed via Atlassian, 30-day trial.
For questions, issues, or feature requests: