Automation: Sprint started/completed does not trigger

[Glenn Ruysschaert]

Hello,

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

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

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

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:

IT scope:

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 

[John Funk · Accepted solution]

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. 

[Glenn Ruysschaert]

Hello @John Funk ,

The checbox is not checked.

Kind regards

[John Funk]

Figured as much. You should check it. And them Update. And then test again. 

[Glenn Ruysschaert]

@John Funk 

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.

[John Funk]

So you checked the box, saved it, and then tried the process again, and it still didn't work? 

[Glenn Ruysschaert]

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

[Glenn Ruysschaert]

Hello @John Funk 

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:

This one got triggered

But the automation that should trigger, does not:

Any ideas?

Kind regards

[John Funk]

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? 

[Glenn Ruysschaert]

Hey @John Funk ,

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.

[John Funk]

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 suggested for a global rule in one of the JAC tickets he mentions above. 

[Glenn Ruysschaert]

Hey @John Funk ,

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.

[John Funk]

Awesome - best of luck!

[Glenn Ruysschaert]

@John Funk 

It seems like changing the scope to Global fixed it.

Thanks for the help

[John Funk]

Great! Glad to hear. 

[Bill Sheboy]

Hi @Glenn Ruysschaert 

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

[Glenn Ruysschaert]

Hello @Bill Sheboy ,

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

[Bill Sheboy]

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/#/