What a Jira time in status dashboard gadget has to do
A report answers a question for the person who runs it. A dashboard answers it for everyone who did not.
That distinction sounds obvious until you watch it fail. A team lead knows exactly where the review bottleneck is — she opens the time-in-status report every Monday, sets the filters, reads the numbers. Then she goes on holiday for two weeks and the knowledge goes with her, because the answer lived in a sequence of clicks rather than on a wall. The question "where does our time go" did not stop being asked; it just stopped being answered.
So the bar for a Jira time in status dashboard gadget is not a chart. It is this: the number is visible before anyone asks for it, it is current without anyone rebuilding a filter, and it means the same thing to everyone who reads it. A gadget that needs interpretation — or worse, needs you to know which caveats apply — is a report with extra steps.
Jira ships several gadgets that circle this territory. They are worth understanding precisely, because each of them answers a real question — just not this one.
What Jira's native Average Time in Status gadget shows
Jira Cloud has a gadget named for the job, and it is the first thing people try. It plots a line chart: for each day in a chosen window, the average time that issues resolved on that day had spent in the statuses you selected. You point it at a project or a saved filter, pick statuses, and set how many days back to look.
Three properties of that design decide what it can answer.
Only resolved issues count. The average on any given day is computed over the issues that got a resolution that day. An issue that has been sitting in Blocked for three weeks contributes nothing until the day it finally resolves — at which point it lands in one day's average and produces a spike. The gadget reports on the survivors; the issues currently stuck, which are usually why you built the dashboard, are invisible to it.
The grouping is by resolution day, not by cohort. Ten issues resolved on the same Tuesday are averaged together regardless of when they were created or how different their paths were. On a quiet day a single old issue owns the data point. The line is honest about what it measures, but what it measures is jumpy by construction.
The status list is instance-wide. When you configure the gadget, the status dropdown offers every status on your Jira site — not the statuses of the project or filter you just selected. On an instance with a few dozen teams that is hundreds of entries, many with near-identical names from workflows you have never seen. Atlassian tracked this as JRACLOUD-77503 and closed it as fixed in 2023; the list is still instance-wide. If your team's In Review shares a name with another team's, you get to guess.
Two neighbouring gadgets are often suggested as substitutes, and neither is one. Sprint Health is a snapshot of the active sprint — progress by estimation, flagged issues, scope change — and it says nothing about durations, so a sprint can look healthy while every issue in it spends two-thirds of its life waiting for review. Filter Results renders a saved filter as a table with columns of your choosing, which is exactly right for "what is currently in Blocked", but Jira does not store time in status as a field: the history records transitions, and durations exist only once something computes them, which is how a Time in Status report is built. No duration field, no duration column.
| Gadget | Answers well | Cannot answer |
|---|---|---|
| Average Time in Status | Trend of average time in selected statuses, for resolved issues | Anything about unresolved issues; anything in business hours; time per status over a filter |
| Sprint Health | Is the active sprint on track by estimation | How long work sits in any status |
| Filter Results | Which issues currently match a filter | How long they have matched it |
The question native Jira dashboard gadgets cannot answer
Put the three together and the hole is still the question that started the dashboard: for this team, this epic, this sprint — how much time went to each status, counted in working hours?
That question has three requirements, and every native gadget fails at least one:
- Time per status, including open issues. The bottleneck is in the work that has not finished. A view restricted to resolved issues shows you last month's problem.
- An arbitrary slice. "The project" is rarely the unit anyone manages. The question is about a team's issues, an epic, a sprint.
- A clock that skips nights and weekends. A ticket that entered Waiting for Customer on Friday evening and left on Monday morning waited either sixty-some hours or almost none, depending on the clock. A dashboard number that silently includes the weekend gets challenged the first time it appears in a meeting — and once a number has been successfully challenged, the dashboard it lives on is dead. People go back to asking the team lead.
The third point is the quiet killer. Native gadgets count calendar time, always. There is no setting that makes them aware of a working day.
How to add a Time in Status gadget to a Jira dashboard
Since version 2.2.0, Time And History puts each of its four reports on a dashboard twice — as a chart gadget and as a table gadget — which is eight gadgets in Jira's picker. Adding one takes four steps:
- Open the dashboard you want it on and click Edit. You need edit rights on that dashboard.
- Click Add gadget and search for Time And History. The picker lists the eight gadgets with a preview of each.
- Pick the chart or the table. Time in Status adds the chart; Time in Status (Table) adds KPI tiles and a table. The same pair exists for Assignee Time, Time to Resolution and Time in Changes.
- Configure and save. Open the gear, choose at least a project, then save and leave the dashboard's edit mode.
The gear holds a subset of the report page's filters: Project, then Epic, Sprint and Assignee as optional narrowing, a Period (the report presets, or a custom range picked on a calendar), the Time format, the View — Chart or Table — and the Visualization — Donut, Bar or Area. That configuration is saved on the gadget instance and is what everyone who opens the dashboard sees. Only people who can edit the dashboard can save it.
The first load of a gadget on a dashboard can take a few seconds while the report is computed. After that the card carries an "Updated 5 minutes ago" label, so nobody has to wonder how old the number is. The full field list is in the dashboard gadget documentation.
Chart gadget or table gadget: which one to add
The chart gadget answers where does the time go at a glance. It aggregates working time per status over every issue matching the gadget's filters — the same whole-filter aggregation as the report's charts, not a sample and not only resolved issues — and renders it as a donut, a bar chart or an area chart.
The table gadget answers how much, exactly. It opens with four KPI tiles — the total time in statuses, issues tracked, the number of statuses, and the average time per issue — over an aggregate table with one row per status and a Total row. Those tiles live in the table gadgets; the report pages themselves do not have them.
Two rules of thumb. A workflow with four or five statuses reads well as a donut; a twelve-status workflow does not, and belongs in the table twin. And if the question is about people rather than statuses, the Assignee Time (Table) gadget expands each person into per-status rows, which is the fastest way to see whose queue the time is sitting in.
How gadget filters work on a shared Jira dashboard
Every gadget shows its current Project, Sprint, Period and Assignee as chips on the card, and chart gadgets add an inline donut / bar / area switch next to them. Both are yours alone: changing a chip or the chart type re-cuts the gadget in your browser session only, it is not written back to the dashboard, and a reload restores what the gear has saved. So a viewer can answer a follow-up question on the spot without disturbing the wall for everyone else. Epic is the one filter that lives only in the gear.
The other link that matters is at the bottom of the card. Open full report opens the matching report page with the gadget's filters already applied — the per-issue table, the other chart types, the footer with Avg, Median, Min and Max per status for the issues on the current page, and the export are one click behind the dashboard. Nobody has to rebuild the filter to drill in, which means the drill-in actually happens.
Per-sprint and per-epic dashboards that survive the first month
A gadget that answers the question is necessary but not sufficient. A few conventions decide whether the dashboard is still being read in November.
One question per gadget. A gadget pointed at a whole project with a twelve-status workflow answers nothing; it is a report squeezed into a tile. Narrow it — one epic, one sprint, one period — and add a second gadget for the second question. A per-sprint row of gadgets with a per-epic row underneath is a dashboard people can scan; one giant donut is not.
Let the chips do the caption. The card already states its Project, Sprint, Period and Assignee, so the scope of the number is legible without anyone having to ask. What the card cannot show is the clock, and that is the thing that gets challenged, so agree it once: durations follow the app's work calendar — business days, per-weekday hours, holidays, a time zone — rather than the raw wall clock, and say so out loud the first time the dashboard is presented.
Keep the units consistent across the wall. The time format is part of each gadget's saved configuration, so two neighbouring gadgets can perfectly well be read in different units. Pick one for the dashboard. Switching between HM, Decimal Hours, DHM and Decimal Days changes only the unit the same calendar-aware working time is displayed in — the underlying value is always the working seconds calculated against your work calendar — with the one caveat that in DHM and Decimal Days a "day" is a 24-hour block of that working time, not one business day.
FAQ
Does Jira have a built-in time in status dashboard gadget?
Jira Cloud ships the Average Time in Status gadget, which charts the average time that resolved issues spent in selected statuses, grouped by the day they were resolved, in calendar time. It works as a trend line for completed work, but it cannot show time per status over a chosen filter, include still-open issues, or count business hours — and its status picker lists every status on the site rather than the ones in your project. For those, you need a Marketplace app's gadget.
Why does the Average Time in Status gadget show every status in Jira?
Because its configuration loads the status list for the whole Jira site. Atlassian tracked the complaint as JRACLOUD-77503 and closed it as fixed in 2023; the list is still not scoped to the selected project or filter. On large instances that makes the gadget hard to configure correctly, since unrelated workflows contribute similarly named statuses.
Is there a free time in status gadget for Jira?
The Time in Status gadget in Time And History is included in the free tier, which covers Jira sites with up to 10 users. Larger sites use the paid plan, which starts with a free trial on the Atlassian Marketplace; the gadgets and the full reports behave identically on both.
Can a Jira dashboard show time in status in business hours?
Not with native gadgets — they count calendar time and have no notion of a working day. Time And History's gadgets use the same calculation as its report pages, which follow a work calendar defining business days, per-weekday hours, holidays and a time zone, so the durations on the dashboard skip nights and weekends when the calendar says so.
Can everyone on the dashboard change a gadget's filters?
Anyone who can see the dashboard can change the chips on a card — Project, Sprint, Period, Assignee — and switch a chart between donut, bar and area, but only for themselves: the change lives in the browser session and disappears on reload. Saving a different configuration in the gear requires edit rights on the dashboard, so the shared view stays what its owner intended.
Put the number where the question gets asked
If the answer to "where is our time going" currently lives in one person's Monday routine, move it onto the dashboard and see how long it survives without them. Add a Time in Status gadget for the chart, a Time in Status (Table) gadget for the exact figures, and one per sprint or per epic rather than one for everything.
Time And History for Jira Cloud is the app that provides them: four reports built from Jira's issue history — Time in Status, Assignee Time, Time to Resolution and Time in Changes — each also available as a chart and a table gadget, all counted against your work calendar. It is free for up to 10 users. Install it from the Atlassian Marketplace, or read the dashboard gadget documentation first.