Jira time in status from a CSV export

Load a Jira changelog CSV with one row per status change and the tool adds up the time each issue spent in every status. You get a per-issue table, mean, median and 85th percentile per status, and CSV downloads.

Everything runs in your browser. Your text and files stay on your device and are never uploaded.

Choose a file, or paste the rows below.

How to use it

  1. Export the status history of your issues as CSV. You need the issue key, the change date, the old status and the new status on each row.
  2. Choose the file or paste the rows. The tool guesses the columns; fix any it got wrong in the Columns section.
  3. Set the options: days or hours, whether 03/04 is March 4 or 3 April, and which statuses stop the clock, such as Done.
  4. Turn on working hours if weekends and nights should not count.
  5. Read the summary table, then download the per-issue CSV to chart or share.

What the file needs

One row per status change, with the issue key, the date of the change, the old status and the new status. Jira's own CSV export lists issues, not their history, so use a changelog export (for example from the Jira REST API, where each issue's changelog lists every status move) and keep the status rows. If your file also has a Field column, only rows where the field is Status are used.

  • Time in a status is the gap between entering it and the next change.
  • Issues that returned to a status add up every visit.
  • Statuses you list as stopped, such as Done, are left out so finished work does not keep counting.
  • Dates without a time zone are all read in one zone, so the gaps between them stay correct. With working hours on, dates that carry an offset, such as +0200, use that offset's clock.

Questions

How do I get time in status out of Jira?

Jira does not show it in a standard CSV export, which lists current values only. Export the change history (changelog) of your issues, for example from the REST API or a report, so each status change is its own row, then load it here.

What columns does the CSV need?

An issue key, the date and time of each change, the status moved from and the status moved to. A field column is optional; when present, only rows for the Status field are used. An issue created date is optional and adds the time spent in the first status.

Which date formats are read?

ISO dates like 2026-10-05 09:00, Jira style dates like 17/Nov/24 10:32 AM, month-name dates and numeric dates. For dates such as 03/04/2026 pick month first or day first in the options.

How are issues still open handled?

Time in the current status runs to the newest date in the file, so export just before you analyze. Statuses you list as stopped, by default Done, Closed and Resolved, are not counted at all.

What does the 85th percentile mean here?

85 percent of issues spent this long or less in the status. Teams use it as a realistic upper bound, since the mean is pulled up by a few stuck issues.

Is my Jira data uploaded?

No. The file is read and calculated in your browser tab and never sent anywhere.

More free tools

All free tools