I found a relevant difference: seems that onprem script aim to sync the whole history of sprints the issue was linked to, while cloud version aim to sync just the current unique link to the open/future sprints.
I also tried to apply logics from the onprem script in cloud but the issue update commit fail due to the value of the sprint field so... I cannot find a way to migrate history of closed sprints the issue was linked in the past.
Hello,
comparing groovy script found here: https://docs.idalko.com/exalate/display/ED/How+to+sync+sprints+in+Jira+Cloud
with script found here: https://docs.idalko.com/exalate/display/ED/How+to+sync+sprints+in+Jira+on-premise
I found a relevant difference: seems that onprem script aim to sync the whole history of sprints the issue was linked to, while cloud version aim to sync just the current unique link to the open/future sprints.
I also tried to apply logics from the onprem script in cloud but the issue update commit fail due to the value of the sprint field so... I cannot find a way to migrate history of closed sprints the issue was linked in the past.
Is there any working way you are aware?
Thanks in advance, BR
We managed using csv import and mapping sprint name (we set in the csv) with destination instance sprint id (found calling Atlassian REST api).