Summary

Issue Description

This KB article is about the following issue:

Rules don't get triggered if the trigger was the result of an action executed by another rule, while rules get triggered when the trigger came from a Jira user. 

Example

Let's assume that the 2 following rules were configured

• Rule 1: Rule that automatically updates the Priority field when another field (for example the End Date field) is updated
  
• Rule 2: Rule that automatically sets the Assignee field of an issue when the Priority field is updated
  

When using the default configuration in the Rule details section, the following will happen:

• If a user manually changes the Priority field of an issue, the Rule 2 will be triggered (an entry will be added to the Audit Log of this rule)
• If the Rule 1 was triggered and changes the Priority field of an issue, the Rule 2 will not be triggered, even though this rule was "supposed" to be triggered when the Priority field is updated

Environment

Any Jira Server/Data Center version from 8.0.0, with any Automation for Jira Version fro 7.0.0.

Cause and solution

By defaults, any automation rule cannot be triggered any other automation rule. The only way to allow an automation rule to be triggered by other rules, is go to the Rule Details section of that automation and to tick the following box:

Allow rule trigger
Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.