Issue History Data Export Through API

The Issue History for Jira API allows teams to programmatically export Jira work item history data for reporting, analytics, and integration with external systems.

Using the API, you can retrieve structured historical Jira data without manually reviewing individual work items or exporting reports through the UI. This makes it easier to build custom dashboards, synchronize Jira history with BI tools, and maintain long-term historical records.

How it works

Prerequisites

In Jira, go to Apps -> Manage apps ->Connected Apps, search for Issue History for Jira (Work Item History), and click on View app details.

In the app Details menu, enable the REST APIs option.

1. Generate a new data source link

Go to the app’s Table View and click the API button.

In the window that opens, generate a new link for your saved preset. For that, select one of the saved views from the list.

After selecting the required view, click the Create button.

You will receive a data source link that you can easily copy.

2. Authorize access

You will also see an action to start authorization. Click the Authorize in the window.

You will be redirected to the Atlassian consent screen, where you need to review the requested access and click Accept.

3. Get your authorization code

After consent is granted, you will be redirected back to the callback page.

The system will display the authorization details you need for the next step.

After that, use the authorization code to request two tokens with an HTTP client such as Postman: an access token and a refresh token.

These tokens are used by your external system or integration to securely call the data source.

5. Use the token when requesting the data source

When your integration calls the generated data source link with a valid access token, the report is calculated at that moment and returned as a JSON response.

What the API returns

The API returns report data as a JSON payload. The report is built on demand.

A generated link will follow this pattern:

CODE

https://<site-name>/gateway/api/svc/<product>/apps/<app-id>_<env-id>/<path>

Copy

The request uses dataSourceId as a parameter.

Permissions and visibility

Where Jira permission enforcement is supported, the data source returns only the work items that the authorized user is allowed to view.

This helps ensure that users only receive data they already have access to in Jira.

Counts and report size

Because the report is generated dynamically during the API request, the final result may differ from the number shown when the link was created.

Troubleshooting

1. I get less data than expected

Possible reasons:

• the authorized user does not have permission to view all work items in Jira

• the count shown during link creation was only an estimate

• the report is too large or too broad for the new dynamic flow

2. The request fails because the payload is too large

Reduce the amount of data in the preset by:

• narrowing the project scope

• shortening the date range

• applying additional filters

3. I completed authorization, but the request still fails

Check that:

• the view needed is saved

• the new data source link is being used

• the access token is valid

• the token has not expired

• your integration refreshes tokens when needed