Sprint change for Issue ticket report

[Harshad Prajapati]

We need to track the history of changes made to the Sprint / Fix Version field for a filtered list of Jira tickets.

The purpose is to understand how the Sprint / Fix Version has changed over time and to report on these changes to Anil Sir as he has asked for this report.

We are looking for a report containing the following details:

• Jira ID
• Summary
• Previous Fix Version
• Date when the previous Sprint / Fix Version was assigned
• New Fix Version
• Date when the new Sprint / Fix Version was assigned

Example:



Jira ID	Summary	Previous Sprint/ Fix Version	Date Assigned	New Sprint/ Fix Version	Date Assigned
PAMIT-12345	Sample Issue	U16 SP2 B35.8.25	10-Jul-2026	U16 SP2 B35.8.26	15-Jul-2026

I currently have standard Jira user access and am able to export only the current Sprint / Fix Version through the CSV export. However, I am unable to retrieve the historical changes to the Sprint / Fix Version field.

Could you please let me know if:

• Such a report can be generated from Jira, or
• There is any supported method or plugin available to extract the Sprint / Fix Version change history for the selected issues?

[Arkadiusz Wroblewski]

Hello and Welcome to Atlassian Community @Harshad Prajapati 

Native ? I don´t think so.

With Rest Api with POST /rest/api/3/changelog/bulkfetch or  GET /rest/api/3/issue/{issueKey}/changelogmaybe.

Or with App from Marketplace

Best,

Arek 🤠

[Gor Greyan]

Hi @Harshad Prajapati

Welcome to the Atlassian Community!

As @Arkadiusz Wroblewski mentioned, there isn't a native Jira report/CSV export that provides the Sprint/Fix Version change history in the format you've shown.

The REST API is the best native option. The issue changelog contains historical field changes, including the previous and new values, so you can retrieve the changelog and filter the results for Sprint and Fix Version changes.

One thing to keep in mind is that the API won't directly return the finished report in your example format. You would need to process the changelog entries and extract.

Issue key | Summary | Previous value | Change date | New value

Since you mentioned having only standard Jira user access, you may also need assistance from your Jira administrator depending on your API access and how you plan to automate/export the report.

[Lalithesh]

Hi @Harshad Prajapati 

Welcome to the Atlassian Community!

Jira's standard JQL export does not include the complete historical changes made to the Sprint or Fix Version fields. It only exports the current values of those fields.

However, you can generate a report using Jira REST API or ScriptRunner (if available) or a marketplace add-on like 'Issue History for Jira'

Thanks!

[Natalia_Kovalchuk_SaaSJet_]

Hi @Harshad Prajapati !

Yes, you can create this type of report using Issue History for Jira (Work Item History) from the SaaSJet team.

In the app, you can select the required project or sprint. Then, use the Column option to include the fields you want, like Sprint and Fix Version. The report will display historical changes, showing the previous value, new value, and the date/time of each change.

After you configure the report, you can easily export the history to Excel or CSV for additional reporting or sharing.

This is especially helpful when you want to track changes in Sprint or Fix Version across various Jira tickets instead of checking the history of each of them individually.

Hope this helps!

[Ivan Manolov _Appfire_]

Hi @Harshad Prajapati,

Two things that should make this a lot less painful, both within reach on standard user access.

First, narrow the list with JQL. For Fix Version there is a history operator, so you don't have to pull changelogs for tickets that never changed:

project = PAMIT AND fixVersion CHANGED DURING ("2026/07/01", "2026/07/31")

Worth knowing that CHANGED is documented as working with the Assignee, Fix Version, Priority, Reporter, Resolution and Status fields only. There is no sprint CHANGED equivalent, so for the Sprint half of the report you go straight to the changelog.

Second, use the bulk changelog endpoint rather than one call per ticket.

POST /rest/api/3/changelog/bulkfetch
{
  "issueIdsOrKeys": ["PAMIT-12345", "PAMIT-12346"],
  "fieldIds": ["fixVersions", "customfield_10020"]
}

It accepts up to 1000 keys per request and filters to up to 10 field IDs, which is exactly your use case. Replace customfield_10020 with your Sprint field ID, which your admin can confirm. Results are paginated, oldest first, and you continue with the nextPageToken from the response.

The permission required is only Browse projects for the projects involved, so a normal account with its own API token can run this. Each changelog entry gives you created plus an items array where every item has fromString and toString, which maps directly onto your columns: previous value, date assigned, new value, date assigned.

Best,

Ivan

[Ivan Manolov _Appfire_]

Following up on my earlier answer, @Harshad Prajapati: if what Anil actually wants to see is how often work slipped between sprints, rather than a full audit trail of every field change, there is a lighter way to get most of the value.

If you're open to solutions from the Atlassian Marketplace, the app my team and I work on, JXL for Jira, is a spreadsheet/table view for your Jira data with a set of computed columns for exactly this.

Alongside the current Sprint you can add First sprint, Last sprint, Number of sprints and Number of closed sprints, then sort by the sprint count to see which tickets have been carried over the most. Fix version columns sit next to them in the same row, and the whole sheet exports to Excel or CSV.

To be straight with you about the limits: JXL's history columns cover status and assignee, so it won't reproduce a previous Fix Version to new Fix Version trail with both dates. For that exact table, the changelog route stays the way to go.

Best regards,

Ivan