Can I run another automation from a manual trigger?

Sarah Isaacs

Hey,

Please can I ask for help. I want to create a manual trigger automation that runs another create automation based on a if statement if the summary contains C2 then run an Automation that is called and contains C3.  or allows them so select an automation that has C3 in its name? And then so on if C3 then C4 etc bascially specific automations based on the name of the task then run the manual trigger from? 

Then a second update on an existing automation that checks a task exists before create it? 

This is an example of my naming: 

Level 1/CTUP/HiLo Writing C2 - Creates Storyboard sub tasks, sends TL email 

Level 1/CTUP/HiLo Writing C3 (Levels 5&6 Percentage Written) - Creates 1st Draft sub tasks, moves to 1st draft column and sends TL email

or

Level 1/CTUP/HiLo Writing C3 - Creates 1st Draft sub tasks, moves to 1st draft column and sends TL email

Within the create issue I'll now need to check if the issue already exists.

any help would really be appreciate thank you

 

This is my automation:

Bill Sheboy

Hi @Sarah Isaacs 

There is rule no action to directly trigger one automation rule from another by-name-of-the-rule.

I have seen some workarounds for trying this type of rule flow, but none are the same as calling a sub-routine to do something and then return to the caller.  A few of them are:

1. The starting rule edits an issue which leads to triggering another, second rule (which detects the issue field change).  In the second rule, the option to allow rule trigger is enabled.
2. The starting rule could use the Send Web Request action to trigger another rule which as been pre-built to use the Incoming Webhook trigger
3. Build a service outside of Jira which does what you need, and call that with the Send Web Request action

The first one will certainly be detected for looping checks, and so could exceed the service limit if it does this many times, such as in a branch or chain of execution.  I have not seen any documentation to learn if triggering a webhook rule from another "counts" for loop detection.

I recommend discussing the scenarios with your Jira Site Admins before trying either of these, as an error could cause various service limit / rule usage problems.

Kind regards,
Bill