Export Jira field change history

Choose work items, review their changes, and download the rows with the context needed to understand them.

The downloadable examples use synthetic data. For subscription costs, see pricing.

Get started

After your Jira administrator installs History Steward, open Apps → History Steward in Jira. Sign in with the Jira account whose permissions you want the report to use. If prompted, allow the app to access Jira on your behalf.

Jira Cloud calls issues work items and projects spaces. The report covers all selected work item types. JQL and technical export columns still use Jira’s API names, such as project and issue_id.

1. Select the work items

Choose a Space, a saved Jira filter, or a JQL query. Select Check work items to see which items are included. For example, project = OPS ORDER BY id ASC selects accessible items in OPS; key = OPS-101 selects one item.

Selection uses the current Jira search result and supports historical JQL operators. It does not reconstruct a past search result or past space membership. Very recent changes may take time to appear in Jira search.

2. Choose dates and load history

Choose Last month, Last 7 days, This month or Custom dates. Both the start and end date are included in the report time zone. A one-day report uses the same date in both fields.

Time zone choices show today’s UTC offset. Report dates use the time zone’s rules for that date, including daylight saving. Select Load history to read the available history. Keep the tab open while it runs; Cancel stops further work.

Existing history from before installation can be included when Jira provides it. History is not a backup of deleted or inaccessible work items.

3. Find the changes you need

After history loads, filter by Fields, Changed by, Before and After. These filters apply to the loaded history. A row must satisfy every filter group; multiple chosen fields or included people match any one within their list.

Equals and Contains compare text exactly and are case-sensitive. Empty Before or After conditions apply no restriction. Selecting no fields matches no rows. Changed by can include or exclude people and apps that appear in the loaded history.

Changing the source, dates or time zone requires checking and loading the selection again. Filtering loaded rows does not fetch older history automatically.

4. Download and read the export

Select Export Excel or Export CSV. Access is checked again before the file is prepared. Work items that are no longer accessible are excluded, and the export is marked partial. A file already downloaded remains under your control.

Work item keys and summaries reflect their values when checked for export. Before and After show values stored in Jira history. They are not reconstructions of the whole work item at that time.

Excel hides technical columns by default. Unhide them for exact UTC timestamps, IDs and the distinction between an empty, null or missing value. On Scope, expand the metadata rows and unhide columns C and D for paths and value types. CSV includes these columns directly; import identifiers as text to avoid rounding long IDs.

Excel values are literal text, not formulas. CSV protects formula-like values with a leading apostrophe. For automated processing, remove exactly one leading apostrophe from a parsed CSV cell when present, then use its state column. Keep the CSV together with scope.json.

Long or unsupported Excel cell values are never silently shortened. If Excel cannot represent a value, use CSV. The workbook is configured for landscape printing; pagination and appearance can vary between spreadsheet applications.

Save a report preset

Save preset saves the current selection, period, time zone and filters. Give a new preset its own name, or explicitly update an existing preset’s settings. Load preset lets you load, rename or delete a saved preset. Loading a preset does not start a report.

You can save up to 20 presets for your account in each installation. Presets are private settings, not shared reports. Relative date ranges update when you use the preset or load history again. History and downloaded files are not stored with it. You can still view and delete your presets if the license becomes inactive.

Limits and partial results

Each run supports up to 1,000 work items and 100,000 field changes. Request, response-size and memory limits can stop a run earlier. Split large selections into smaller reports using spaces, filters or JQL.

Complete means the available history for the accessible selection was processed to a confirmed end. It does not promise every change ever made in Jira or an atomic snapshot of permissions and data.

Partial means selection, reading or the access check could not finish completely. Read the reason, narrow the selection or retry. Exporting a partial result requires an explicit choice; the filename and report details keep that status. An empty partial report does not mean there were no changes.

This app does not calculate time in status, restore deleted work items, export comments or worklogs, reconstruct past JQL selections, or send scheduled reports.

Need help?

See support and troubleshooting. For data handling, read Privacy and Security.