I have a an old Sprint with end date coming January (2023-01-18). It should have had end date the past January (2022-01-18) and hence it is now overlapping with all sprints during this year and we do not expect to get it to show up correctly until 18th January next year when it has ended.
This give negative side effects on for instance Roadmap overview since it does not show the individual 3 week sprints we are now working in.
I have been told that the only way to get it corrected is to have a support case with Atlassian and then they can change the date. I'm in process having our JIRA admin to issue such a support ticket but I simply wanted to ask the community if there are any other faster ways to fix this.
Hi @Erik Sundberg ,
I think there's no way to change the end date of a closed sprint directly. But you can reopen the sprint and update the end date field.
Thank's for the suggestion Tharaka!
I will bring that up with our project manager and JIRA admin. Might be doable since we any way do not use JIRA for any statistics on burn rate etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Youy are realy Great Tharaka!!
The suggestion you gave worked like clockworks!!!
Our project manager did as you suggested and now all solved.
Realy good of you. Must say I'm dissapointed that the Atlassian support where not able to come up with this smart yet easy to implement solution!! Also Atlasian product management shouild be able to give this solution as input on the raised tickets for ading a function for date correction.
Again many thanks to you Tharaka!!
Have a nice day.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You’re most welcome @Erik Sundberg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm afraid there's no way to edit/modify the end date of a closed sprint. This is a frustrating topic for many Jira cloud users.
There is a feature suggestion open for this: https://jira.atlassian.com/browse/JSWCLOUD-16331
Please vote and feel free to watch the issue for updates!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Hamza Chundrigar
I had a look at that one that have been starving for 5 years and it also linked another one from about 3 years furhther back.
Seems we siply have to live with the misstakes done, in my case by someone that was working on this project amost a year ago.
Lets keep fingers crossed our happy time will come.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
See solution by @Tharaka_Hettiarachchi above that worked nicely above (Reopen sprint and close on correct date).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.