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. Release notes for Unitix Flow and Manage Board 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 built from the issue changelog: per-status durations, waiting columns, business-hour calendars and XLSX/CSV export.
Exclude weekends and holidays from Jira time in status with a work calendar — business days, hours, time zone, holidays — and see which statuses shrink.
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), created-to-done in business hours with reopened issues kept apart (Time to Resolution), and the changes to the standard Jira fields (Time in Changes).
Where the workload lands Time to Resolution and the SLA gap Time in Changes in the documentation