Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How do I modify sprint end date for a closed sprint?

We forgot to end a sprint on the correct date.

The problem is that the end is always set to the date when the sprint is closed.

How can i set the end/close date for a past/closed sprint? (these are not shown in the backlog)

I know that i can reopen a sprint but when i close it again it will always take the current date and i cannot set it to the correc date.

3 answers

1 accepted

Hi @Sanjana _Alacriz_ 

thanks for the info.

This should work, but of course i would prefer to edit this dates directly in Jira.

Like Brock Jolet likes this
0 votes
Craig Brunetti
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 24, 2023

What confuses me, is how Atlassian thought to have us define a Sprint's date range (because it does have us declare the start and end when we MAKE a sprint), but then when we hit the Close button, that date range isn't the source of truth.

So we collect an end date, so that the burndown can draw correctly, I get that. And then when I close, there's a new date, so they are separate reasons. Except, close a sprint with a later date, and that later date then gets used to draw the burndown! Not so separate.

Why is this so hard, Atlassian? Clearly the appropriate behavior is to stick to the date range that was declared when the sprint was defined, NOT depend on when a human being happens to come along a hit a button.

This is not working for cloud I presume.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events