After re-opening a closed sprint the burndown chart updated x axis to show current date

[Ilona]

[Trudy Claspill]

Hello @Ilona 

Welcome to the Atlassian community.

That is working as designed. When you reopen a sprint that changes the end date to the sprint. The end date of the sprint will be updated to the date when you close the sprint again.

[Ilona]

On a separate project, my colleague opened a sprint, removed an issue that didn't belong and when they closed the sprint, the end date, which was 4 sprints ago, didn't change.  Perhaps it has to do with how the Jira board is set-up?

In my example, I have a few issues that rolled-over to the following sprint so when I re-opened the sprint,
1. the burndown chart was refreshed and now shows the actual dates those "In Progress" issues were closed (even though these occurred after the completion of the sprint referenced and
2. the velocity chart was updated and Sprint 42 now appears to be after Sprint 45.

[Trudy Claspill]

I can't explain what you say happened for your colleague. My experience with Jira Cloud has been that if you reopen a closed sprint, make changes, and then close the sprint again then the end date of the sprint is set to the current date and the sprint activity is updated so that it looks like the sprint was open the whole time.

And the Velocity chart will show the last 7 sprints based on completion date, I believe, and ordered by completion date.