How to export Jira issue history to CSV
An auditor, a manager, or your own post-incident review asks a reasonable question: “show me everything that changed on this issue, and who changed it.” You open the issue’s History tab, see it all on screen — and then look for the export button that is not there. Here is how to actually get Jira’s change history out as a CSV.
Why this is harder than it should be
Two Jira features look like they should solve it, and neither does:
- The issue History tab shows the full field-change log — old value, new value, author, timestamp — but it is a read-only on-screen view. There is no export, and no way to pull it across many issues at once.
- Jira’s CSV / Excel export (from a filter or the issue navigator) exports the current state of fields — the values as they are now. It does not include the change history, so it cannot tell you what a field used to be or who changed it.
That leaves the REST API — the changelog endpoint can return history per issue, but stitching it into a usable, resolved CSV across a project is a scripting job, not something you do between meetings.
The straightforward way: capture it, then export
Trailkeeper shows each issue’s field-change history with status, priority and custom-field names resolved to readable text, and lets you export to CSV straight from the issue panel — free, capped at 500 rows, uncapped on the paid tier. It opens straight in Excel or Google Sheets.
What that gives you that the native path does not:
- The change trail, not the snapshot. Old value → new value, with the author and timestamp, rather than just today’s field values.
- Across issues, not one at a time. The paid tier runs a change report scoped by project or JQL for an audit, instead of reading one History tab after another.
- Evidence that lasts — on the paid tier. Paid adds continuous capture to an independent store, so the history survives later edits or deletion (for issues changed since install) — see recovering a deleted issue for exactly what that does and doesn’t cover.
The takeaway
Jira shows you issue history but will not export it, and its CSV export is current-state only — so the on-screen trail you can see is the one you cannot easily hand to an auditor. Capture the field-change history with an audit-trail app and export it to CSV, and “show me what changed and who did it” becomes a one-click answer that opens in a spreadsheet. For the difference between Jira’s two history surfaces, see Jira audit log vs issue history.
Frequently asked questions
- Can you export an issue's history from Jira Cloud?
- Not cleanly — the History tab on an issue shows changes on screen but has no export button, and Jira's CSV export covers current field values rather than the change-by-change history. Getting the change history out needs the API or an app.
- Does Jira's CSV export include change history?
- No. Jira's built-in CSV and Excel export give you the current state of each field, not who changed what and when. For the change trail you need an app that records field-change history and exports it.
- How do I get Jira history into Excel?
- Capture the field-change history with an audit app, then export it to CSV — which opens directly in Excel or Google Sheets — so you can filter, pivot and keep it as evidence.
- Why would I export issue history?
- For audits and compliance evidence, for post-incident review of exactly what changed and when, and to keep a record that survives even if the issue is later edited or deleted.