Automation rules stacking/triggering other rules. Automation Rule #1 has a scope & trigger event which fires an action. . . . based on that action, Automation Rule #2 then triggers due to it's scope being the action of #1.
Example; if 1 rule is programmed to update the assigned to, the state & the priority of a ticket. and a 2nd rule exists that states if an incident is updated to Priority=Critical, then do an action. Those two rules working in tandem would be very beneficial.
Today that is not the case - each AR Scope is singular in nature. Due to this, a higher volume of automation rules is necessary to capture multiple scopes.
