Notes from the team behind Time And History for Jira Cloud: how long issues really sit in each status, what work calendars do to your numbers, and what the issue history can tell you — plus what we got wrong along the way. Engineering notes on how Unitix Flow assembles a release branch and on what a Jira Server board has to get right live here too.
New here? Start with the Time in Status guide, see how Time And History works, read the docs, or install it from the Atlassian Marketplace — free for up to 10 users.
How a Jira time in status report is calculated from the issue changelog, how to build one in Jira Cloud, read the Avg/Median footer and export it.
Jira status change history: what the History tab answers, where it stops, and how to read who changed what, when, and how long the old value lasted.
Jira transition count report: how to count status transitions per issue, which reopens it covers, and how to read the rework columns without a History tab.
Jira average time in status: why one stuck issue doubles the mean, what median, min and max are each for, and which issues every number actually covers.
Jira time in status export to Excel: why the native CSV has no durations, the changelog formula route, a clean XLSX — and the same file emailed weekly.
Jira time between two statuses: why the changelog is the only source, how to add an In Progress → Done column, and what first exit and last exit measure.
A Jira time in status dashboard gadget puts working time per status where everyone sees it: what native gadgets miss, how to add one, and how to defend it.
How long every issue sat in To Do, In Progress, Blocked or Review, counted in business hours from Jira's issue history — as a donut, bar or area chart, or as a table with Avg, Median, Min and Max per status.
Read the Time in Status guideBusiness days, per-day working hours, a time zone and holidays that repeat every year. Attach a calendar and the nights, weekends and public holidays stop counting towards every duration in every report.
What work calendars changeEvery report is built from the Jira changelog: who held an issue and for how long (Assignee Time), the working time to each resolution with reopened issues kept apart (Time to Resolution), and the changes to the standard Jira fields (Time in Changes).
Where the workload per assignee lands Time to Resolution and the SLA gap Time in Changes in the documentation
