Changing the Date of a Closed Sprint

Daniel Herdenez February 28, 2024

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!

1 answer

1 vote
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 28, 2024

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.

Daniel Herdenez February 29, 2024

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

Daniel Herdenez February 29, 2024

image.png

Photo of the report dates

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 29, 2024

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.

Daniel Herdenez February 29, 2024

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

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 29, 2024

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.

Mary Heather Cox
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 2, 2024

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events