Reverting changes

[Tim Williams]

Hi All, somehow a bunch of old completed sprints were moved to the latest sprint. I have no idea how to undo those changes. Can someone assist in showing me how to track history so I can revert old work back to the appropriate sprint/timeline?

Thanks!

[Nazarii Sobchuk _Grandia Solutions_ · Accepted solution]

Hi @Tim Williams ,

Happy to help you with resolving this one.

You can start with taking a close look at their history section to find when / by whom the Sprint field was updated. 

You can check this by opening a History tab in one of your affected Jira issues here:



Afterwards, scroll down and check a line that relates to the Sprint field:



Here you'd see few things:
- Who made an update
- When update was made
- What was the original value (left side: Hub Sprint 10) and what it changed to (right side: Hub Sprint 10, Hub Sprint 11)

From here you should be able to understand the previous Sprint value and update accordingly.

Hope this helps!

Kind Regards,
Nazar

[Tim Williams]

Very helpful. The only problem now is that the sprint they should be in is closed, and it doesnt seem like there is any way to reopen and move the tickets back. Not sure what to do. 

[Yuliia_Borivets__SaaSJet_]

Hi @Tim Williams 

If you need to track the history of multiple issues, you can try the Activity Stream gadget on the Jira dashboard. It allows you to filter issues by project and dates and check all past activities.

Another more flexible solution might be Issue History for Jira app developed by my team. It allows filter issues by sprint or JQL (as shown below) and add a sprint column to check sprint changes specifically.

Also, our team recently released the bulk revert feature, but it works only for active or future sprints, not closed ones.

[Trudy Claspill]

Hello @Tim Williams 

Has there been a change to the mapping of statuses to columns in your scrum board? Specifically, have the statuses mapped to the right-most column changed?

Or, has another Scrum board been created that uses a filter that references the same issues, and has a different status/column mapping configuration?