It is possible to edit the closing date of the sprint

[Antonio Burgos Vieyra]

I have some doubts.

First, what is the end date of the sprint for?

This is because when I close the sprint it takes the date on which I click the button, not the one I have programmed.

In such a case it is possible to edit that date in Jira cloud managed by company.

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

The end date of a sprint is for marking the end date of the sprint.

Sprints are a time-box. They have a start and an end.  Jira assumes the end date of a sprint, because it should be predictable - sprints are supposed to be the same length, and the next starts at the end of the last, so there's a fixed predictable cadence.

But if you start or end a sprint outside the cadence, that's fine, you've got different data and you're telling Jira that.  Jira simply overwrites its assumption with your real-life data.  You can't directly edit that, because you'd be telling lies, but you can re-open a sprint, and close it again later.

[Antonio Burgos Vieyra]

My case is that I want to regularize them, my sprints have an end date and due to my sprint planning they should have ended a month ago, but due to specific cases they are ending now. So they are already expired. And at the end of these sprints I would like the dates that I schedule to appear

[Nic Brough -Adaptavist-]

That would be misrepresenting what you did.  You can't expect an issue tracker to lie about what happened - the whole point of them are that they record what you worked on.

There's no reason to leave a sprint open and have it end weeks after the end data.  That's missing the whole point of doing sprints.  But if you've got yourself into a position where people are extending active sprints and hence making that mess, then yes, I understand why you're asking, but the answer is still to end the messed up sprints now and move on to the next ones.  And get your scrum masters to do their job properly - starting and ending the sprints at the right time.

[Antonio Burgos Vieyra]

thanks, in that sense, is it possible to save those start and end dates that you schedule in a custom field?

[Ram Sai]

end date automatically updates during the starting of the sprint. it depends on how you set it up for ex: most have 2 weeks sprint. but few have 3- or 4-weeks sprint. however, when you end the sprint before the actual sprint end date, you are forcing the sprint to end it early hence it takes the end date as day you click on end sprint. 

[Antonio Burgos Vieyra]

In a case where I am on the day I programmed to end the sprint, is the closing automatic or do I still have to do it manually?

[Nic Brough -Adaptavist-]

You should always do it manually.  Ending a sprint is the responsibility of the ream.

[Ram Sai]

You do have an option to end it automatically. But as Nic said you should always end it manually. It's supposed to be done as a team.

[Antonio Burgos Vieyra]

thanks, in that sense, is it possible to save those start and end dates that you schedule in a custom field?

[Ram Sai]

You can try going to edit sprint option and you might be able to see that option to edit sprints. I say may be because it again depends on whether you have the permission to do so or not.

[Antonio Burgos Vieyra]

I want to copy these two dates into fields within the incidents, in order to make a report. I have already validated all the incident fields in the report, but that data does not appear.