Tagline: Burndown, velocity, cumulative flow, cycle time, time in status, aging WIP, throughput, epic and release burndown, pivot tables, KPI gauges, a team board, a work breakdown tree, worklog reports, a countdown, a world clock and a TV wallboard — native Jira dashboard gadgets that run entirely on Atlassian. Free for 10 users, then US$0.60 per user per month.
Install from the Marketplace listing, or in Jira go to Apps → Explore more apps and search for Agile Gadgets for Jira. You need to be a Jira administrator. No configuration is required before first use.
Open Apps → Agile Gadgets for Jira in the top navigation. It has three tabs:
Agile Gadgets adds twenty dashboard gadgets to Jira. Point each one at a board, a project, a saved filter or any JQL query, and it draws the chart a delivery team actually argues over in a stand-up: what is left in the sprint, how much the team really finishes, where work piles up, how long things take, which items have been in flight too long, and whether the release date is credible.
Every chart is rebuilt from Jira’s own issue history rather than from a snapshot, so a burndown knows what the scope was on the day, a velocity chart knows what was committed at the sprint’s start instant, a cumulative flow diagram knows which column each issue sat in three weeks ago, and throughput counts the day an issue crossed into done rather than the day someone set a resolution date. Days are bucketed in the viewer’s own Jira timezone using calendar arithmetic, so a chart does not shift by a day for a colleague in another country or across a daylight-saving boundary.
Everything runs on Atlassian infrastructure. There is no vendor server, no data export, and no egress: the app reads Jira as the person looking at the dashboard, so a gadget can never show anyone an issue they could not already open.
Sprint and delivery
- Sprint burndown / burnup — remaining work falling to zero, or completed work rising to meet scope, in story points or issue count. Ideal line on calendar or working days. Scope changes are marked with the issue keys that were added, removed or re-estimated, and the baseline is taken at the sprint’s start instant, so planning-day additions count as commitment rather than churn.
- Velocity — committed versus completed for the last N closed sprints (1–24), with scope added and removed in between, per-sprint attainment and running averages. committed + added − removed always reconciles.
- Sprint health / commitment reliability — not “how much is done” but “how much is done compared with how much of the sprint has gone”, plus the mean attainment of the last N sprints and its spread. A team delivering 100/40/130/60 has the same average as one delivering 80/80/80/80 and is nothing like as predictable, so the spread is reported as prominently as the mean.
- Epic burndown / burnup — one epic burning down, with its children joining and leaving drawn as scope change.
- Release / version burndown — a fix version burning down towards its release date, with historical fix-version membership taken from the changelog, and an optional cross-project query for a release several teams contribute to.
- Release readiness — what is left, the run rate the date demands, the run rate the team is actually achieving, a forecast date laid over working days, and a verdict. When there is no recent throughput there is no forecast: “never” printed as a date is worse than an honest blank.
Flow and ageing - Cumulative flow diagram — how much work sat in each workflow status at the end of each day, for a window of 2–365 days, replayed from status history. Bands never go negative and always sum to the day’s total; work in a status no column claims is reported rather than dropped. - Cycle time / lead time — every issue that finished in the window, as a run chart against P50/P85 reference lines with a 10-issue rolling mean, as a histogram, or as a true dot-per-issue control chart on the export page. Percentiles are nearest-rank, so “85% of items finish within P85 days” is literally true of the listed issues. Groupable by assignee, issue type, priority, component, label or parent. - Time in status — how long issues sit in each status, with percentiles taken over issues rather than over segments, and a working calendar that can skip nights, weekends and named public holidays. Each issue’s per-status durations tile its life exactly, so the rows always sum to the total. - Aging work in progress — every unfinished item against the status it is in and how long it has been in flight, with P50/P85/P95 bands drawn from the cycle times of work that actually finished. When nothing has finished recently the gadget says so rather than quietly using a distribution biased towards young work. - WIP run chart / throughput — work in progress per day, or work finished per day or week, replayed from status history, with Little’s-law flow time reported so nobody has to work it out on a whiteboard. - WIP by status — what is in progress right now, per status, with the age of the oldest item and the average age.
Structure and reporting - Issue statistics / pivot — count issues or sum story points by any field, in one or two dimensions, as a table, bar chart, pie chart or heatmap. Row totals, column totals and the grand total always reconcile with the cells, and multi-valued fields such as labels are counted once per value with that stated in the gadget. - Work breakdown structure — the whole Initiative > Epic > Story > Sub-task tree, with totals rolled up at every level. A node’s rolled-up total is always its own size plus its children’s, and a parent cycle from a migrated site is broken rather than followed. - Epic progress — done, in progress and to do per epic, computed from the epic’s children. Each issue is grouped under its top-most ancestor, so a story with sub-tasks does not become a phantom epic of its own; an epic’s own status never inflates its own progress. - Team board — an agile board’s own columns, WIP limits and cards, on a dashboard or a wall-mounted screen, with swimlanes by assignee, parent, priority or issue type. Issues in a status the board does not map are surfaced, not hidden. - Worklog / timesheet report — time logged by person or by issue over a range, bucketed by the civil day the person was working in the viewer’s timezone. Read-only: a reporting gadget that can edit worklogs is a reporting gadget that can silently rewrite someone’s timesheet.
Wallboard furniture
- KPI gauge / formula — a formula over a query, drawn as a gauge with a target, a big number, or a five-star rating, with up to eight more number tiles beside it. The formula grammar is arithmetic over count, and sum/avg/min/max/median/p85/p95 of estimate, doneEstimate, done, inProgress, toDo, ageDays, cycleDays and leadDays. Nothing is executed; a bad formula cannot take a wallboard down, and an empty result shows “–” rather than a flattering zero.
- Countdown — days, hours and working days to a date, in the timezone you choose, with an optional progress bar from a start date.
- World clock — the time where your colleagues are, up to eight places, and whether they are likely to be at their desks.
And the app’s own page — a full-bleed TV wallboard that plays saved panels on a rotation and refetches as it runs, a PNG and CSV download for any gadget, and named shared filters: save a JQL query once under a name, point any number of gadgets at it, and edit it in one place.
Great Gadgets is the incumbent: 4.4★ from 49 reviews, roughly 3,700 installs, US$1.00 per user per month annually on its Standard tier at 100 users, with worklogs and timesheets held back for a pricier Advanced edition.
We now match every gadget on its list — sprint, epic and release burndown/burnup, velocity, CFD, cycle time trend, control chart, histogram, time in status, WIP aging, WIP run chart, throughput, work breakdown, pivot table and chart, wallboard, formula gauges, countdown, regional clock and worklog reports — in one edition, at roughly half the price. We beat it on scope-change markers that name the issues, a commitment baseline taken at the sprint’s start instant, percentile bands taken from finished work, a working calendar with holidays, viewer-timezone day buckets, and “Runs on Atlassian” with no data leaving the site. Two gadgets have no counterpart there at all: sprint health with its reliability spread, and release readiness with a forecast date.
What they have that we do not, plainly: a controller gadget that filters other gadgets live on the same dashboard. Forge gadgets are isolated and cannot message their neighbours, so this is a platform limit rather than a decision; the shared-filter store is the closest the platform allows, and it ships. Beyond that, two presentation differences: the pivot is configured from a form rather than by dragging fields, and the scatter control chart and file downloads live on the app’s own page rather than inside a gadget, because a native Forge gadget has no scatter mark and cannot write a file. We would rather keep “Runs on Atlassian” than put an iframe on your dashboard.
| Users | Price |
|---|---|
| 1–10 | Free, all twenty gadgets |
| 11+ | US$0.60 per user per month monthly, or US$0.50 per user per month annually |
Why: Great Gadgets charges US$1.00 per user per month annually (US$1.20 monthly) up to 100 users — US$1,200 a year for a hundred-person team — and splits timesheets into a pricier Advanced edition. We ship one edition at half the headline price with the same free tier, because the app is a Forge app with no infrastructure of our own to pay for. At 100 users that is US$600 a year against their US$1,200, with the worklog report included.
One gadget covers up to 1,500 issues where it has to replay issue history (burndown, velocity, flow, cycle time, time in status, aging, WIP) and up to 3,000 where it only reads current field values (pivot, epic progress, hierarchy). Beyond that the gadget says so and asks you to narrow the source rather than quietly charting a subset. Boards, sprints, projects, versions, epics and fields are picked from lists in the gadget’s own configuration form; the JQL option accepts any query you can already run.
Read-only. The app never writes to Jira and stores no issue data.
read:jira-work, read:jira-user — issues, changelogs, worklogs, fields, statuses, projects, versions and the viewer’s timezone, through the Jira platform REST API.read:board-scope:jira-software, read:board-scope.admin:jira-software, read:sprint:jira-software, read:project:jira — boards and sprints, through the Jira Software agile REST API, which publishes only granular scopes. Board configuration is read for the board’s saved filter and its estimation field; .admin is Atlassian’s name for that read, not a write.storage:app — three things only: named shared filters (a JQL string), saved wallboard panels and wallboards, and a one-slot per-person clipboard used to carry a gadget to the export page. No issue data is ever stored; every saved query is re-run as whoever is reading it.All computation happens inside Forge on Atlassian’s infrastructure. The app declares no external egress, stores no issue data, and calls Jira as the viewing user so Jira’s own permissions apply to every number on every chart.
Email support with a one-business-day response.