+1

batch update removes all the sprint and apply the new sprint.

+1

+1 Please... such an essential feature! You've been "gathering interest" for 11 years now...

If someone is looking for a workaround, Issue History for Jira might be the solution. It lets you filter by sprint and add fields like sprint or others to view changes across all issues in one place. 

The add-on is also compatible with the Data Center version.

Here is an answer from the Community where you can see report screenshots:

https://community.atlassian.com/t5/Jira-questions/Sprint-modification-report/qaq-p/2644696?utm_campaign=subscription_search_answer&utm_content=topic&utm_medium=email&utm_source=atlcomm#U2645419

Yes please 

+1 please god, especially when your tool allows someone to accidentally move 600 rows from the backlog into the wrong sprint.

+1 shocked to find that this isn't already supported

+1, when can we expect this to be delivered please. Also, is there any workaround here?

+1

+1. Want to use this in order to search for issues that were originally planned in the sprint, but were taken out.

+1

+1. Want to use this in order to search for issues that were originally planned in the sprint, but were taken out.

+1. Want to use this in order to search for issues that were originally planned in the sprint, but were taken out.

+1

+1 , this is really a needed requirement, with which we will be able to identify the committed items during sprint start. Basically identify the scope churns

+1

+1 truly mind boggling that this is missing

+1

+1

+1

+1

+1

+1

+1

+1

agree

Agree, this is an essential part of tracking for us.

So essential feature yet you prefer to focus on bells and whistles mostly in your releases. It is sad. 

1+

+1

This is important to query the original commitment of a sprint. It is such a basic and important property of a agile setup that it is a HUGE lack that this is not supported. How is this issue not fixed years ago??

+1 Dear Atlassian. Do you have any ETA on this CR?

Thanks

+1

+1

+1

Pretty please? +1

+1

+1

+1

+1

+1

+1

+1

+1

+1

When producing retrospective reports this would be amazing, as currently the JIRA sprint report page is the only place this information would be viewed, and I know many places that have their own retrospective/report pages in something like Confluence.

This is essential, need to be able to show which issues added to or removed from the sprint.

+1 Agree, this should be included in the basic functionality

This is a pretty significant as it does not show us sprint planning changes.

Yes, I agree.  It looks like people have complained about this for a long time without any response from Atlassian.  It is ridiculous that there is no way to find the sprint history.

This should be included as OTB functionality. It is very surprising that is is not. 

Adding my vote - I need this to identiofy issues that did not complete in a sprint and were moved to a future sprint.

Would be super useful, as we want Devs to have the ability to update and change the sprint, but we want to make sure that PMs and leads are aware, and notified in case there is any sprint clean-up or balancing required.

I agree that this is a feature which should already be available to manage sprints well. Scope change is something that needs to be alerted in every way possible!

I am responsible for setting up the sprint and getting the business to approve it. Another team can move tickets out of a sprint that could not be completed in the sprint. I need to find them and report on them. I also need to know if any tickets were added to the sprint say after the team started to do development.