Time in Status reports and dashboard gadgets for Jira Cloud

Yes. The Time in Status table has a footer with the average, median, min and max time per status for the issues on the current page, and KPI tiles above it — total time in statuses, issues tracked, statuses and average time per issue — captioned “This page”. Switch to chart mode and the same tiles are captioned “Whole selection” and cover every issue your filters match. Averages follow the work calendar, so weekends and holidays are not counted.

Before you quote one, it is worth reading why the average and the median disagree, and which issues each number covers.

Yes. Set the filters on a report page, open Scheduled Reports and create a schedule: any of the five reports, daily, weekly or monthly, at the start date, time and time zone you choose. The report is generated on that clock and mailed as an XLSX to up to ten recipients you type yourself. The filters are frozen when the schedule is created, and every run is listed in Export History. A run collects as the schedule owner, so recipients see the owner’s view of Jira.

On Time in Status, open Between statuses and add a pair — In Progress → Done. Each pair becomes a column of working time per issue, with average, median, min and max in the footer for the issues on the current page, and it travels into every export and into a Time in Status schedule. Choose first exit (later loops ignored) or last exit (every loop counts). Up to ten pairs, saved for you.

The Transition Count report counts every status-to-status transition per issue: one column per pair, a Total column per issue and a TOTAL row for the issues on the current page. It is how you count reopens and rework without reading changelogs by hand, and it exports to XLSX or CSV.

Which reopens that number actually covers, and how to read the backward columns, is the subject of the guide to the Jira transition count report.

Yes — since version 2.2 Time And History adds eight gadgets: a chart and a table for Time in Status, Assignee Time, Time to Resolution and Time in Changes. Transition Count and Between Statuses live on the report pages and have no gadget yet.

Adding one takes a couple of minutes, and the walkthrough covers the chips, the gadget settings and who can change what.

Yes. Work calendars define business days, per-day hours, a time zone and holidays that repeat every year, and every report that measures time counts business hours only. The choice is a personal setting, remembered for you across sessions and applied to every report and gadget you open, without changing anyone else’s results.

How much it moves the numbers is the subject of a worked example of the same sprint on two clocks.

Press Export on any of the five reports and choose Excel (XLSX) or CSV; chart mode adds a PNG of the open chart on any report. The export covers all issues matching the filter, not just the visible page, and builds in the background.

What lands in the file, sheet by sheet, is set out in the guide to exporting Jira time in status to Excel.

The Time in Changes report lists every change from the issue changelog, and each entry shows who made the change, when, the old and new value, and how long the old value lasted. It covers status, assignee, priority, summary, issue type, reporter, description, labels, due date and resolution. Expand an issue to read its full history, field by field, and use History by Fields to choose which fields are listed — custom fields appear in that list but produce no rows.

The History tab, its four limits and how to read a change row are set out in the guide to Jira status change history.

Time to Resolution keeps each resolution pass in its own column, named after the resolution value with an ordinal — Done 1st, Done 2nd — so an issue that came back twice shows three resolution times side by side. A column appears when a resolution is set, so that count covers the reopens that were resolved again; for the return trips themselves, open ones included, Transition Count counts how many times each status pair occurred per issue.

Reading across that row rather than down to the total is the point of the reopened-issue walkthrough.

Time And History does not define SLA rules, but Time to Resolution gives you the number an SLA is measured against: the working time to each resolution, per issue, on your work calendar. Compare it with your target for any Jira Software project — no Service Management licence required.

Where that number and a real SLA part company is the subject of Jira time to resolution: the SLA gap nobody measures.

Yes. All five reports filter by project, sprint, epic, reporter, assignee and date range, and the eight dashboard gadgets by project, sprint, epic, period and assignee. So you can compare one sprint with the previous one, or see where the issues of an epic waited longest. Transition Count is the one report with no work calendar and no time format — it counts events, so no working time is involved.

No, and that is deliberate: every Jira read runs as the person viewing the report, so each viewer sees only the issues their own Jira permissions allow. Access settings decide per Jira group who can open the reports at all. The one exception is a scheduled report: the run collects as the schedule owner, so its recipients see the owner’s view.

Pricing follows Atlassian’s standard Cloud tiers: free for up to 10 users, then a per-user monthly subscription with a free trial for larger sites. Subscriptions, trials, renewals and refunds are handled by Atlassian through the Marketplace, in your Atlassian billing console.