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

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

donhames
Contributor
November 11, 2024

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?

2 answers

1 vote
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 11, 2024

Hello @donhames 

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

0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 12, 2024

Hi @donhames 

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

 

donhames
Contributor
November 12, 2024

@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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events