one rule triggers another rule directly

[Eric Jahn]

Can the 'Then' action of a rule directly specify another rule to be triggered (i.e. daisy-chain rules)?

The reason I am asking, is that I have a global automation rule where a source ticket's status change, changes the fields in a destination ticket.  I have a second project-level automation that listens for that same field to change.

When a user directly/manually changes the field change, the second project-level automation is triggered, as expected.

However, when the global automation changes the same field normally that triggers the second project-level automation, the second project-level automation is *not* triggered as expected.

Can automated events not "daisy-chain" to trigger subsequent automations?  I would think they should.

[Bill Sheboy · Accepted solution]

Hi @Eric Jahn 

No, a rule cannot call another rule.
Yes, a rule can trigger another rule through its actions.

This second behavior is disabled, by default, to prevent looping and run-away situations.

When you want the actions of one rule to trigger another, the "downstream" rule which will be triggered needs to have the option "Allow Rule Trigger" enabled in its details at the top of the rule.

Consider side-effects and impacts of doing this, as other rules could now trigger such rules.

Kind regards,
Bill

[Eric Jahn]

Thank you @Bill Sheboy for the clarification!