Select work items.
Choose a space, a saved Jira filter or a JQL query. Set the dates and report time zone, then check which work items are included.
Issue history.
Ready for review.
Export Jira issue history to Excel or CSV. Compare before and after, and see who changed each field and when.
Free for up to 10 Jira users. View pricing.
Projects, filters or
JQLBefore & after
valuesExcel & CSV
export
From selection to export
in three steps.
Choose work items and dates, review their field history, and download the changes you need.
Find the changes.
Review the available history. Filter by field, who made the change, or before/after value.
Download your report.
Download an Excel file or CSV ZIP with report details and any gaps clearly marked. Save a report preset for next time.
A clear row
for each change.
Choose a field to filter this compact preview. Download the matching files generated by the app from the same synthetic data.
Field change historyAugust 2026 · UTC
Scroll across to compare Before and After
| Work item | Changed (UTC) | Changed by | Field | Before | After |
|---|---|---|---|---|---|
| OPS-101 | 2026-08-05 09:15:00 UTC | Alex Morgan | Status | To Do | In Progress |
| OPS-101 | 2026-08-05 09:15:00 UTC | Alex Morgan | Assignee | Empty | Mia Chen |
| OPS-101 | 2026-08-08 14:30:00 UTC | Mia Chen | Due date | 2026-08-15 | 2026-08-22 |
| OPS-102 | 2026-08-12 10:05:00 UTC | Alex Morgan | Customer tier | Standard | Enterprise |
| OPS-102 | 2026-08-16 11:45:00 UTC | Release automation | Priority | Medium | High |
| OPS-101 | 2026-08-20 08:00:00 UTC | Mia Chen | Status | In Progress | Done |
| OPS-102 | 2026-08-21 13:00:00 UTC | Not provided | Legacy field | Null | =SUM(1,2) |
3 work items checked · 2
with matching changes · August
2026
Synthetic example · generated by Issue History Export · no connection to your Jira site
Know what your export covers.
Each export includes the query, date range and report details, so you can see what the rows cover.
The work items you selected
Use a space, saved filter or JQL query to select the work items you can access. The date range limits the export to changes that happened during that period. Historical JQL operators remain supported.
See when results are incomplete
If the app cannot finish loading history, loses access to selected work items or reaches a processing limit, the report is marked Partial. You’ll see the reason before exporting. Details of work items you can no longer access are excluded.
Values as Jira stores them
Before and After preserve the values returned by Jira history. IDs and value metadata help distinguish an empty value from a value Jira didn’t provide.
Straightforward pricing.
All features included. Pricing is based on your site's licensed Jira user count, not on the number of exports or the file format.
Free for up to 10 Jira users
$0.01per user / month
For every licensed user on sites above 10 users. Prices are in USD and exclude taxes.
Billing follows your site's licensed Jira user count, not how many people open Issue History Export.
Atlassian Marketplace handles trials, subscriptions and billing.
More about Issue History Export for Jira
Issue History Export reads the issue history of Jira issues you can access in Jira Cloud and exports each recorded field change, custom fields included, to Excel or CSV.
This app turns field changes you can access on your cloud site into a clean file. Issue history for Jira gives admins, team leads, auditors and project managers a structured review without editing anything. Every row shows the item, time, author, field, before value and after value, custom fields included.
Start with your scope: a space, saved filter or JQL query, plus an inclusive date range and report time zone. Before loading Issue history Jira data, confirm which items are included.
- Pick a space, saved filter or JQL query
- Set dates and time zone
- Check included items before loading
Each update becomes one row. Filter that change history by field, author or value. Jira view issue history then focuses on one field or person without touching source data, while Jira issue history report output keeps before-and-after values visible. That helps when you need to see what changed instead of reading a long activity feed.
- Jira export issue history when you need those updates in a file
- Jira export history as a general export workflow
- Jira export ticket history when your scope holds tickets under review
Choose output for your next step. An Excel workbook contains Changes and Scope sheets; a ZIP holds CSV plus scope.json. Both keep query, period, filters and report details. This supports export Jira to Excel workflows and CSV analysis, with context preserved.
- Workbook and CSV share identical columns
- Jira field change history is what gets exported
Who relies on it
- Auditors confirm who changed a priority, status or owner and when
- Team leads review what moved during a sprint or release
- Admins answer Jira history questions about custom field updates without screenshots
- Compliance owners keep a dated record for each review cycle
- Support managers trace when an assignee or priority switched during an escalation
Example row
Item SUP-118, field Priority, before Medium, after High, its author, and time in your report time zone.
Scrolling through an activity tab works for one ticket. For a quarter of updates across a whole project, a file you can sort, filter and archive is easier to share with reviewers and keeps the evidence in one place.
Why Scope matters: it records query, period and filters, so reviewers can rerun that report next quarter and compare results line by line.
Save up to 20 private report presets. Relative periods update when you use a preset, so recurring setups follow your current period instead of an old fixed range. Presets store settings only; source data stays untouched. A monthly preset with a relative period gives your team a repeatable review without rebuilding the query.
- Ticket history here means recorded updates for items in your scope
- How to view Jira ticket history: select scope, period and filters, then load changes
If you are searching for audit trail software, a Jira Excel plugin, a Jira reporting app or Jira reporting plugins, this app has a specific scope: it exports the field changes available to you. It does not add a new activity source or site-wide audit record.
This app is read-only; files are built in your browser. Access is checked again before details are included. Unavailable details are left out, and partial results carry clear reasons. That makes Jira audit trail review possible from exported updates without claiming every event is present.
- Deleted items cannot be recovered
- Time in status is not calculated
- Your site-level Jira audit log stays as it is
- Jira activity log is not a separate feed of this app
- The audit log is a site-level administrative record, which this app does not replace
Quick answers
What does an export contain?
One row per recorded change with item, time, author, field, before value and after value, custom fields included.
What if some details are no longer available to me?
Access is checked again, unavailable details are excluded and partial results are marked with reasons.
Does it calculate time in status?
No. Only recorded changes are exported.
Can I start from a saved filter or JQL query?
Yes. Use a space, saved filter or JQL query, then set an inclusive date range and report time zone.
Where are files created?
In your browser. The app is read-only and does not change work items.
Jira history
export FAQ
What the report includes, what it leaves out, and how to get started.
Contact Issue History Export supportCan I export several work items at once?
Yes. Choose a space, saved Jira filter or JQL query, then check the selection. Processing limits cap a selection at 1,000 work items and retained results at 100,000 field changes; other limits may stop a run earlier, and large selections can take many minutes. Narrow the selection or explicitly export a partial result. See the report limits.
What is in the Excel and CSV files?
Excel contains a Changes sheet and a Scope sheet with report details. CSV downloads as a ZIP containing changes.csv and scope.json. Both formats include one row per field change, with before and after values and technical metadata.
For native options and a worked example, read how to export Jira issue history to Excel or CSV.
Are issues and work items the same thing?
Jira Cloud now calls issues work items. History Steward exports their field change history, including changes to tasks, bugs, stories and other work item types. Older Jira documentation may also call a space a project.
Can I export history from before installation?
Yes, when Jira still provides it and you have access. History Steward reads existing field history; it does not need to have been installed when a change happened.
Is this the same as the Jira audit log?
No. This report covers field changes on selected work items. It does not export the site administration audit log, comments or worklogs, and it cannot recover deleted work items.
Can it reconstruct last month’s search results?
No. JQL runs when you check the selection and can contain historical operators such as WAS or CHANGED. The report does not reconstruct the full membership of a space or search result at an earlier date.
Does it run on a schedule?
No. Start each report yourself and keep the tab open. Report presets save your settings; relative periods such as Last month update when you use the preset or load history again.
Is Issue History Export free?
Issue History Export is free for up to 10 Jira users, with every feature included. Larger sites need a paid subscription through Atlassian Marketplace. See per-user rates.
Give your next review
a clearer history.
Explore the sample report, then download the Excel or CSV files.
View the sample report