This worked for us. Note that it's the START_DATE and COMPLETE_DATE columns that define the beginning and end of the sprint. I'm not sure what the END_DATE is. Maybe someone from Atlassian can illuminate us.
Also, be aware that the date is stored as a unix timestamp. To arrive at the correct value, you need to convert your desired date/time to GMT and then convert to a unix timestamp.
This is absolutely achievable without DB manipulation - at least in the current version.
All you need to do is go to your sprint report, find the sprint you wish to edit via the drop down menu. Once you have that selected there's a more options / kabob menu icon (3 horizontal dots) which will allow you to reopen that sprint. At this point you can then visit your backlog and change the dates of the sprint and then re-close.
Your current sprint (if you have one active), will remain unharmed, unedited and can continue to feature in active sprint view, upon the close of retro-active sprint.
I think this misses the point. You can edit the END_DATE like this, but you will also cause the COMPLETE_DATE to be changed to the date/time that you re-closed the sprint after performing this edit, which is even later than the date on which the sprint work was actually terminated. It is the COMPLETE_DATE that affects your analytics (as mentioned by Dave Thomas) and i think the END_DATE just represents your original plan. Once the sprint is finished, the END_DATE is just window dressing.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events