Issue Done but Sprint not completed error

[Atakan Olgun]

Hello dear atlassian team,

I have a problem like this; We also want the sprint to end automatically after the work is taken to the completed step on the board in the Jira Cloud environment.

Should automation be written on the subject or is there a simpler way?

Best regards,

[Trudy Claspill]

Hello @Atakan Olgun 

Typically Sprints have an end date set, and the sprint is ended on that date regardless of the state of the issues in the sprint. If there are incomplete issues in the sprint then they are moved either to the backlog or another sprint at that time.

Can you tell us what problem you are trying to solve by keeping your sprint open until all the work in it transitions to done, rather then having a defined end date for the sprints?

[Atakan Olgun]

@Trudy Claspill  hi again, 

First of all, thank you for your quick return.

In fact, the demand is literally like this, they want the sprints to end automatically when the work is marked as done on the board.

Best Regards

[Trudy Claspill]

There are no automation functions for completing sprints. 

One purpose of using sprints is to determine how much work a team can complete in a given amount of time (velocity). This is done by setting a time frame for the sprint and then seeing how much work gets done. Having variable duration sprints based simply on the completion of the work defeats the Velocity aspect of using sprints.

"They" have told you the solution they want. You should instead be encouraging them to define the problem they are trying to solve, so that the problem can be addressed appropriately.

Perhaps the use of Sprints is the wrong methodology for this team.

Take a look at the responses on this other post where the question was about automating the starting of sprints.

https://community.atlassian.com/t5/Jira-Core-Server-questions/Jira-Automation-to-start-and-complete-the-sprint/qaq-p/2149913

[Nic Brough -Adaptavist-]

I completely agree with Trudy here, but I want to expand a bit.

There is no automation for "complete sprint" because it should always be done by a human.  Ideally, it is your team's scrum master when the team has agreed that the sprint has ended (even when stuff is still open) during the retrospective, or whatever other gate the team has decided upon.

It is not something you should automate.

Imagine the a case where the team commits to completing ABC-44, ABC-45, ABC-46, and ABC-47 in a 2-week-long sprint that is "Tuesday lunchtime" to "Tuesday lunchtime in a fortnight".  If the team does well and completes everything by lunchtime on the second Friday, an automation would close the sprint at the wrong time and leave your people with two days of dead time before the next sprint starts.  Your scrum master has lots of options on how to do it, but it absolutely should not be automated, the team needs to talk about it.