Have multiple triggers for a single flow in jira automation

[Omer Meshar]

We are using automation quite a lot, and we have a few scenarios where we want to do something specific (same flow) but have different triggers for it.
These triggers include events and scheduled runs, and can be different from one to the other in:

• The timing (when to do it)
• The filter (JQL - which set of issues to do it on)

We currently have a few copies of the same automation rule, each one with a different trigger, and we were wondering if it wouldn't be better to have a single flow (conditions and actions) that can be used in multiple rules or even better, in a single rule with multiple triggering mechanisms.

[Marc -Devoteam-]

Hi @Omer Meshar 

This not an option, an automation can only have a single trigger.

[Bill Sheboy]

Hi @Omer Meshar 

As @Marc -Devoteam- describes, there is no automation rule trigger to cover both scheduled and work item events.  There is a multiple-event trigger, and in my opinion I recommend never using that one due to racetrack timing problems, possible multiple triggering defects, unknown side effects, etc.

Without seeing the specifics of your rules and the scenarios, I recommend pausing to understand the problem being solved by the rules...and thus decide if some of them can be combined in ways to eliminate any duplication.

For specific workarounds to reduce rule / logic duplication, those tend to be complicated.  For example:

1. First, start with the above recommendation to analyze the rules to look for commonality and merging opportunities
2. Use a bunch of rules with different triggers, and have them all "call" a common rule with an Incoming Webhook trigger using the Send Web Request action 
3. Build an external service endpoint, host that, and have the rules call that directly with Send Web Request action 
4. Investigate when a custom Forge application could create a rule action to do what is needed

Regardless of the approach used, combining rules may lead to unintended consequences: more complexity, more difficult maintenance, rule processing side effects, difficultly in detecting and solving problems from overlaps, unnecessary permission granting, etc.  Please consider discussing this with your peer Product Admins to help understand the risk / rewards involved.

Kind regards,
Bill