Jira Automation Rules No Longer Triggering As Expected
Asked by luke.vo:

Up until mid August our Jira automation rules worked, however now we're experiencing inconsistent outcomes. Something likely changed in the Jira Cloud backend and we're having trouble configuring our automation rules to consistently work as expected.

<br />

Background:  
We have two jira automation rules that worked without issue until recently.

<br />

Automation rule 1 (Update Issue Type):  
When an issue is created  
If the creator is not one of list of users  
Then the edit the issue filed to be of Issue Type

Automation rule 2 (Send Slack Message):  
When an Issue is created  
If the Issue Type is of Issue  
Then send a web request to a slack channel  

<br />

<br />

Result:  
When a jira card is created, the issue type was automatically updated to be of issue type, which triggers the second rule. However, now it appears the flow no longer works.  

It's likely that automation rule 1, now performs an "Issue Updated" action, so rule 2 is never triggered.  

We've added issue updated to the rule trigger so that it is now "Issue Created OR Updated", but the outcome still appears to be inconsistent. With some events triggering Success and others reporting No Actions Performed.


Answers:
author: Josh Costella
body: Hi [@luke.vo](/t5/user/viewprofilepage/user-id/5576997)

Are you able to provide screenshots of how the automations are currently configured?

Are you able to view the audit logs of the automations and see if any configurations were changed in them recently?

comments: author: luke.vo
body: Hi [@Josh Costella](/t5/user/viewprofilepage/user-id/1172532) ,  

I've attached the latest rule configurations with redacted info.  

Item 1:  
The long list of "Status is not one of" was added to mitigate duplicate slack notifications because of the new "Issue Updated" trigger.  

The value in "labels contains none of" is an internal team label. For simplicity we can define that as "myteamlabel". It does not seem to have an impact on successful or failing triggers.  

Item 2:  
I unfortunately cannot view the rule history edit log. But can confirm that we only began changing things after rule 2 stopped working mid August.  

![AutomationRule1.png](https://community.atlassian.com/t5/image/serverpage/image-id/343910i8BFC1F4D5784FAD5/image-size/large?v=v2&px=999 "AutomationRule1.png")![AutomationRule2.png](https://community.atlassian.com/t5/image/serverpage/image-id/343911i164514B4A327E0AF/image-size/large?v=v2&px=999 "AutomationRule2.png")


author: Josh Costella
body: Hi [@luke.vo](/t5/user/viewprofilepage/user-id/5576997)

Is this a global automation or is it for a specific Jira project? I would condense this down to a single automation rule. Add the Webhook action to the bottom of the Interrupt Work automation. Add in any additional conditions you need to from the other automation.

If you need to keep them seperate:

Is this Issue Type that gets updated to, is that the only way this specific issue type is ever used? Or could people still create tickets with this issue type directly?

When it comes to the Slack message, is there a specific status you would only want the slack to be sent for? Instead of excluding, just do equals and pick your status.

For the Slack automation:

* Move the Issue Type equals condition to be the first condition.
* Update Status condition to be equals and pick the specific status it should be. (remember: it would only be a status that belongs to the workflow for that specific issue type)
* Update the Slack automation to use this trigger:

![field value change.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/343931iFBC0A21CB15232DB/image-size/large?v=v2&px=999 "field value change.jpg")

* And make sure the box at the bottom of the Rule Details is checked.

![allow other.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/343930i7973EFEEA7DD2EFE/image-size/large?v=v2&px=999 "allow other.jpg")

Now this automation will only run when the issue type is updated via the Interrupt Work automation.


author: luke.vo
body: This automation is scoped to a single Jira Project. I took your recommendation and consolidated the action into a single automation rule. This approach appears to be working well so far.  

Separately, we have other automation rules that I've enabled the "Check to allow other rule actions to trigger.." button on.

This checkbox appears to be a new setting, or maybe I had missed it previously somehow. I'm hoping it sorts out what appears to be a race-condition type of issue between the rule that changes issue types and the rules that send notifications.  

In summary, thank you for your time and recommendations. This can be considered resolved.  


Tags: cloud

jira-cloud