Hello community,
I am seeking guidance on how to change the date of a sprint that has already been closed. I encountered a situation where a sprint, originally scheduled to end on January 31 of this year, was extended for a few more days due to an unexpected influx of bugs that needed attention. As a result, the sprint concluded in mid-February, but the sprint configuration retained the initial date.
Upon further inspection in the project timeline, I noticed that the tasks addressed within the extended timeframe, particularly in February, lack the corresponding timeline representation. None of the user stories, bugs, and other items are correctly reflected in the project timeline, as the sprint erroneously shows a conclusion date of "January 31."
I would like to know if there is a way to modify the date of this closed sprint to accurately reflect the closing date. Additionally, I am curious to find out whether this can be done from the administrator profile of my entity or if I need to seek assistance from the support team.
I appreciate any insights or assistance you can provide regarding this matter.
Thank you!
Hello @Daniel Herdenez
Welcome to the Atlassian community.
No, it is not possible to do that.
The Start Date of a sprint will be automatically set to the date you actually click the Start Sprint button.
The End Date of the sprint will be automatically set to the date you actually click the Complete Sprint button.
This happens regardless of the dates that you fill into the fields for Start and End Date for the sprint. What you fill in will be automatically overwritten with the current dates when you click the Start Sprint and Complete Sprint buttons.
You cannot manipulate those dates.
You can reopen a closed sprint and then re-Complete it, and that will update the sprint end date to the current date, when you are again clicking the Complete Sprint button.
While using Jira's Sprint Report feature, I observed that the displayed Sprint End Date corresponds to the date when the sprint was initially configured to End, rather than reflecting the actual date when it was marked as completed. This observation has led to some discrepancies in our historical sprint data representation.
I'll try to open the Sprint and trying to modify the Sprint End Date before closing it again.
Thanks for your time
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The reported end date is the date a user actually clicked on the Complete Sprint button. It does not retain the planned End Date. That gets overwritten.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Understood, but I clicked 'Complete Sprint' on February 7th, and the reported end date did not overwrite. The Sprint's configuration date was what's displayed in the photo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hm, that is unusual.
It has always been my experience that the planned End Date of the sprint is overwritten by the current date when the Complete Sprint button is clicked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Coming in late here, but I believe it depends on if the sprint was a 2 week sprint where you enter the start date and it autocompletes the end datetime, versus a custom sprint, where you enter it.
2 week sprint - doesn't overwrite planned end datetime
Custom sprint - does overwrite planned end datetime
Consistency is key. Pick 1 way and make that standard across the org.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.