Automation: Sprint started/completed does not trigger
Asked by Glenn Ruysschaert:

Hello,

I have an automation which creates some tickets in a new sprint, after completing a sprint.

![Screenshot 2024-07-03 at 15.02.57.png](https://community.atlassian.com/t5/image/serverpage/image-id/333291i977E84C06B149B53/image-size/large?v=v2&px=999 "Screenshot 2024-07-03 at 15.02.57.png")

I noticed for two sprints already, this has not been triggering anymore, even though it used to work on other boards (the IT Board is a new board).

For example today I completed and ended a sprint, this sprint just started

![Screenshot 2024-07-03 at 15.02.39.png](https://community.atlassian.com/t5/image/serverpage/image-id/333292iB4BCC3618B0C3BF8/image-size/large?v=v2&px=999 "Screenshot 2024-07-03 at 15.02.39.png")

But in the audit logs it does not appear for the automation

![Screenshot 2024-07-03 at 15.04.25.png](https://community.atlassian.com/t5/image/serverpage/image-id/333293i8CD815FE3406DCA3/image-size/large?v=v2&px=999 "Screenshot 2024-07-03 at 15.04.25.png")

To double check I created 2 test automations, one with global scope and one with IT scope. These would print a log when the sprint starts.

After starting the sprint, they did not run.

Global:

![Screenshot 2024-07-03 at 15.04.52.png](https://community.atlassian.com/t5/image/serverpage/image-id/333294iF3B3D563B48B112D/image-size/large?v=v2&px=999 "Screenshot 2024-07-03 at 15.04.52.png")![Screenshot 2024-07-03 at 15.05.10.png](https://community.atlassian.com/t5/image/serverpage/image-id/333296i6BB0B0B819241456/image-size/large?v=v2&px=999 "Screenshot 2024-07-03 at 15.05.10.png")

IT scope:![Screenshot 2024-07-03 at 15.04.57.png](https://community.atlassian.com/t5/image/serverpage/image-id/333295i15E7EC173F2DF765/image-size/large?v=v2&px=999 "Screenshot 2024-07-03 at 15.04.57.png")

![Screenshot 2024-07-03 at 15.05.02.png](https://community.atlassian.com/t5/image/serverpage/image-id/333297i6A249E3D00EFE13C/image-size/large?v=v2&px=999 "Screenshot 2024-07-03 at 15.05.02.png")

This leads me to believe something might be wrong with the board (Software Project type). But I cannot figure out what.

Does anyone know why my automations aren't triggering?

Kind regards


Answers:
author: John Funk
body: Hi Glenn,

Not sure what might be happening to trigger the new Sprint, but it might be that the automation rule is checked to be allowed to run when something else triggers it. Take a look at the Rule Details and see if the box is check to allow it to be triggered by another option.

![Automation Rule trigger box.png](https://community.atlassian.com/t5/image/serverpage/image-id/333298i1D7DC58DA8ACED72/image-size/large?v=v2&px=999 "Automation Rule trigger box.png")

comments: author: Glenn Ruysschaert
body: Hello [@John Funk](/t5/user/viewprofilepage/user-id/7148) ,

The checbox is not checked.

![Screenshot 2024-07-04 at 09.16.45.png](https://community.atlassian.com/t5/image/serverpage/image-id/333450i4F3610F6EEB2DA33/image-size/large?v=v2&px=999 "Screenshot 2024-07-04 at 09.16.45.png")

Kind regards


author: John Funk
body: Figured as much. You should check it. And them Update. And then test again.


author: Glenn Ruysschaert
body: [@John Funk](/t5/user/viewprofilepage/user-id/7148)

Hello,

I tried this automation with a different board (other rule actions unchecked), and there the sprint trigger works.

So it seems it is only on this specific board where the trigger does not seem to work.


author: John Funk
body: So you checked the box, saved it, and then tried the process again, and it still didn't work?


author: Glenn Ruysschaert
body: For the current sprint that is active I cannot complete the sprint and start a new one, as this is an actively used sprint by our IT team. That's why I tried with a different board on which can be experimented.

So to try it again on this specific board, I will need to wait until the sprint is actually done (2 week sprints).


author: Glenn Ruysschaert
body: Hello [@John Funk](/t5/user/viewprofilepage/user-id/7148)

We started a new sprint, on the board where the automation does not work.

With "allow other rule actions to trigger this rule", the rule does not get triggered.

I have a test automation in place:

![Screenshot 2024-07-25 at 09.58.29.png](https://community.atlassian.com/t5/image/serverpage/image-id/337814i4D0461A9D09A6AF1/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 09.58.29.png")

This one got triggered

![Screenshot 2024-07-25 at 09.59.42.png](https://community.atlassian.com/t5/image/serverpage/image-id/337815iF8EB87533FD260E5/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 09.59.42.png")

But the automation that should trigger, does not:

![Screenshot 2024-07-25 at 10.00.35.png](https://community.atlassian.com/t5/image/serverpage/image-id/337816iFC11BA020E47FC09/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 10.00.35.png")

![Screenshot 2024-07-25 at 10.00.56.png](https://community.atlassian.com/t5/image/serverpage/image-id/337817i3EC54E47FC623081/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 10.00.56.png")

Any ideas?

Kind regards


author: John Funk
body: That first rule will not trigger the second rule if that is what you are expecting. What is causing the the sprint to get Completed? Do you have evidence of the Sprint being completed?


author: Glenn Ruysschaert
body: Hey [@John Funk](/t5/user/viewprofilepage/user-id/7148) ,

No, they are separate automations, not linked to each other.

I set up the "Test sprint started" automation, as evidence that when I close a sprint it gets detected. All it does is log the sprint.

But the other automation, does not get triggered (along with some others that are very similar, they all just make some tickets for the next sprint).

So now I have evidence (because of the test automation), that when I complete a sprint, it triggers automations. But for some reason, not all automations get triggered and I can't understand why.


author: John Funk
body: So bottom line is that a Sprint completed action will trigger an automation rule, but a Sprint started action will not. Is that correct?

If so, wondering if you could do some type of workaround where you set the value of a custom field when the Sprint is completed. Then when you Start a Sprint, you somehow read the value of that field and trigger a rule based on that.

Or maybe try the workaround that [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) suggested for a global rule in one of the JAC tickets he mentions above.


author: Glenn Ruysschaert
body: Hey [@John Funk](/t5/user/viewprofilepage/user-id/7148) ,

I have now changed the scope in rule details for the automation that is not triggering to "Global", with the when sprint completed still on the "IT Board".

When this sprint completes, I will check again (as this sprint is currently in use by the team).

I will post the results when I know more.


author: John Funk
body: Awesome - best of luck!


author: Glenn Ruysschaert
body: [@John Funk](/t5/user/viewprofilepage/user-id/7148)

It seems like changing the scope to Global fixed it.

Thanks for the help


author: John Funk
body: Great! Glad to hear.


author: Bill Sheboy
body: Hi [@Glenn Ruysschaert](/t5/user/viewprofilepage/user-id/4054693)

Are your rules triggered for Sprint Started and Sprint Completed using **global-scope**? If so, there are known defects / limitations for those:

<https://jira.atlassian.com/browse/AUTO-1047>  
<https://jira.atlassian.com/browse/JRACLOUD-80707>  
etc.

A workaround I found for these was to use a global, incoming webhook, triggered rule to perform what is needed, and then set up a site, outbound webhook for the needed sprint events to trigger that rule. I covered the details in that second suggestion.

Kind regards,  
Bill

comments: author: Glenn Ruysschaert
body: Hello [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) ,

The automation is not global scope, but for a single project:

![Screenshot 2024-07-25 at 10.00.35.png](https://community.atlassian.com/t5/image/serverpage/image-id/338070i2AEA87812050B1F8/image-size/large?v=v2&px=999 "Screenshot 2024-07-25 at 10.00.35.png")

![Screenshot 2024-07-03 at 15.02.57.png](https://community.atlassian.com/t5/image/serverpage/image-id/338071i22286EF91238802C/image-size/large?v=v2&px=999 "Screenshot 2024-07-03 at 15.02.57.png")


author: Bill Sheboy
body: Thanks for that information, Glenn.

If these are project-scope rules, and the the sprint completion is done manually (i.e., not by another rule), yet it is still not triggering, I recommend working with your Jira Site Admin to submit a support ticket to Atlassian to identify the cause: <https://support.atlassian.com/contact/#/>


Tags: automation

board

cloud

jira-cloud

sprint