Is there a way using automation to schedule the closing of a sprint and starting a new one?

[Don Hames]

I want to set a specific time and date to close an open sprint and start the next one. Can this be done with automation?

[Trudy Claspill · Accepted solution]

Hello @Don Hames 

Automation rules do not include actions to Start or Complete sprints.

There is an API endpoint that can be used.

https://developer.atlassian.com/cloud/jira/software/rest/api-group-sprint/#api-rest-agile-1-0-sprint-sprintid-put

You could call that endpoint through a Send Web Request action in an Automation Rule. However according to this issue that endpoint does not include a way to specify what to do with incomplete issues when closing a sprint.

https://jira.atlassian.com/browse/JSWCLOUD-16588

[Marc -Devoteam-]

Hi @Don Hames 

As @Trudy Claspill mentioned, this is not an option via automation.

I personally think it would also be bad practice, as on closing a sprint what to do with the open issues when the sprint closes.

If multiple sprints have been planned, which one to start first.

And many more questions and actions, that in my opinion should lay with the scum master/product owner

[Don Hames]

@Marc -Devoteam-—Devoteam The problem I am trying to solve is that we have scrum teams working on the same product in four different time zones. Having an automated closure set with the least impact on the teams would be ideal for keeping sprint opening/closing on track and not just selecting one of the time zones to perform that task.

The time zones span up to 18 hours, which varies from location to location. So, the current sprint needs to be closed when the first few teams have left for the day, and the remaining teams are just getting started or have only started a few hours before.

We have several sprints queued up since we are a Scaled Agile shop running PIs, so knowing the next sprint is not an issue.

I hope this adds some context to my question. Thanks.

[DOUGLAS THOMPSON]

I know this is a year old, but... we're coming across a similar issue.  We do the exact same steps every sprint stop/start.  This is available in the 'server' version, why not the 'cloud'?  Anyone who has done anything with automation knows you need to be careful -- this is no different.  Now we will need to write our own tool that leverages the REST API to do what in my opinion should be an available action in Jira automation.  OR, better yet, in the cloud, permit auto-managed sprints the same as what is currently available in Jira Server.

[kh_jbau]

@DOUGLAS THOMPSON, this topic has been locked because the thread has become a bit dated. If you’d like to keep the conversation going or have additional questions, we encourage you to start a new topic. You can read more about necro posting (“raising threads from the dead”) in our Community Guidelines.

Thanks!