Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

how automatically start and stop sprints same day every week

Hi...I need some guidance about whether it is possible to automatically start and stop our sprints without any manual intervention. All our sprints start Thursday and end Wednesday the following week. Can something like that be accomplished with scriptrurner? Our JIRA instance is a Data Center instance with 2 nodes, version 7.1.4. Scriptrunner is 4.3.13


Thank you for your assistance


2 answers

1 accepted

1 vote
Answer accepted

Hi Tomas,

Interesting question / automation smile

Probably you will need one or two ScriptRunner Service running a script every <Choose day>. The script for closing a sprint should be something like 

import com.atlassian.greenhopper.service.sprint.Sprint
import com.atlassian.greenhopper.service.sprint.SprintManager
import com.onresolve.scriptrunner.runner.customisers.PluginModuleCompilationCustomiser
import com.onresolve.scriptrunner.runner.customisers.WithPlugin

def sprintServiceOutcome = PluginModuleCompilationCustomiser.getGreenHopperBean(SprintManager).getAllSprints()

if (sprintServiceOutcome.valid) {
    sprintServiceOutcome.getValue().findAll { it.state == Sprint.State.ACTIVE }?.each { updateSprintState(it, Sprint.State.CLOSED) }
else {
    log.error "Invalid sprint service outcome, ${sprintServiceOutcome.errors}"

def updateSprintState(Sprint sprint, Sprint.State state) {

    def sprintManager = PluginModuleCompilationCustomiser.getGreenHopperBean(SprintManager)
    def newSprint = sprint.builder(sprint).state(state).build()
    def outcome = sprintManager.updateSprint(newSprint)

    if (outcome.isInvalid()) {
        log.debug "Could not update sprint with name ${}, ${outcome.getErrors()}"
    } else {
        log.debug "${} updated."

So the above script is a guide on how to update sprints. I suppose it will require some more logic, but you can build on this. Please let me know if you need further assistance.

regards, Thanos

Hello Thanos...thank you for your reply...thats great!

I kinda get the logic behind that script but I do have a couple of questions. The idea is that the script has to "loop" and find all active sprints and close them so I dont see any looping in that script. And the sprint names change every week so I see in that script def SPRINT_NAME = "Sample Sprint 2", but I cant put a fix sprint name, can I? The sprint names change every week and the script should find all active sprints and close them the day the script runs, thats the idea.


Thank you very much for your help




Hey Thomas, 

I updated the script above in order to close all the active sprints. 

The script to make active future sprints should be very similar. You will need to 'play' with the states.

Hi Thanos...thank you very much for your help.

I will give it a try and let you know how it went. 

Thank you

Hi Thanos...I just wanted to let you know that I was able to test the script to automatically close all active sprints and it worked as a charm! Thank you very much for your assistance.

I will try to create one to activate future sprints and let you know if I have any questions.


Thanks a lot for your help!

Hi there...I have a question regarding this can I see the sprints that were closed when the script runs? is there any log I can check to see if the script ran, if there were any issues, and the sprints that were closed?


Thank you

hi Tomas,

You can add in the each closure a debug message

log.debug "Issue key to be updated : ${it.key}"

And then you can check your Atlassian logs. First you have to set the debugging level for JIRA to DEBUG

Hey @Thanos Batagiannis _Adaptavist_ 

Thanks for the above you mentioned in your comment we need to add a service and it will run at regular basis to close the sprint.

We are looking like whenever the sprint close/complete date will reach the sprint should auto close.

There is a feature request directly related to this question that you can vote for it:

I think this really needs to be a built-in feature for Jira.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

Introducing External Collaboration for Confluence

We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...

215 views 0 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you