How to track issues moved sprint to sprint

[Mitchell, William]

Hi all,

As part of my new role I have been tasked with trying to track work in a report that is moved between sprint to sprint.

Is there a way to use a JQL function, so that work can be tracked if it is moved from:

Sprint 1 -> Sprint 2

and

Sprint 1 -> Sprint 3

Thanks,

Will

[Bill Sheboy]

Hi @Mitchell, William -- Welcome to the Atlassian Community!

Here are some follow-up questions to help selecting a solution: when do you want to do this, and how often?

If you want to do this just after a sprint finishes...perhaps as input to a retrospective, you could use JQL such as this to find issues in a sprint that closed and are now in another sprint:

project = myProject
 AND sprint IN closedSprints()
 AND (sprint IN openSprints() OR sprint IN futureSprints())

If you need to do this often and need to look back in history, consider these options:

1. use the Atlassian provided Excel or Google Sheets add-ins to build a spreadsheet to parse and report on the sprint field
2. use Automation for Jira to detect the condition and update custom fields you add to support reporting
3. use the REST API to pull (or use a webhook to push out logs), and extract the data into another reporting tool
4. use a marketplace add-on for purchase to enhance reporting

Please note: The sprint field can be cleared/edited, just like many of the fields in Jira.  When that is not a concern any of these methods can help.

Best regards,
Bill

[Yuliia_Borivets__SaaSJet_]

Hi @Mitchell, William 

I think Issue History add-on will be helpful here. You can see all changes that have been made to issues by any user. If you add a sprint column, you'll see what sprints an issue was or is for now. 

Try if it will be useful for you. This app is developed by my team, so let me know if you've got any questions.

[Mohamed Benziane]

Hi @Mitchell, William 

There is no native JQL for that, but you can try this workaround posted by Ignacio

https://community.atlassian.com/t5/Jira-questions/search-issues-that-were-not-closed-and-moved-to-another-sprint/qaq-p/1168177

You can also use the REST API to look into the history to field the value that was in the sprinf field

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-changelog-get