Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can I use automation rule to trigger another automation rule?

Edited

When using Automation for Jira, can I use automation rule to trigger another automation rule?

For example:

I have rule that creates "Task A" when I create "Story B"

Also, I have a rule to create "Story B" when I create "Epic C".

 

I would expect that whenever I create "Epic C" it will trigger the "Task A" rule as well

 

6 answers

1 accepted

7 votes
Answer accepted

Hi Itay!

Yes you can allow this by checking the box next to Allow rule trigger in Rule details.

Project_automation_-_JIRA.png

Hope that it answered your question :)

works like a charm :)

Thanks!

Thanks!

Like Robin Flood likes this

Hi Guys,

 

This is what I'm trying to achieve:

I have 4 rules that must be executed following a specific order:

Rule-1, Then after completion

Rule-2, Then after completion

Rule-3, Then after completion

Rule-4

All of those rules have the same trigger: "When issue is created"

 

Can I achieve this in a consistent way or not?

I did this with labels. Rule 1 added a label that caused rule 2 to trigger. Rule 2 would clear rule 1s label so things didnt get messy, then rule did its thing and added a second label, etc...

Not pretty, but it worked!

Like Robert Horan likes this
Robert Horan Marketplace Partner Sep 20, 2021

@Chris Carpenter I love this idea.  One quick question - when all is cleared do the temporary labels still appear in the lookup for labels?

Hey @Robert Horan!

They dont actually. Here's an example of a rule I set up to auto assign bugs to the assignee of the story that the bug was linked to:

2021-09-20 14_15_51-2021-09-20 14_12_53-Project automation - Prodigy JIRA.png ‎- Photos.png



The label applied by the rule is "---assignee" where --- is the project name. That label always shows up as "new" when you type it into the label field on a jira ticket, since it never exists on a ticket in our system for more then a few seconds

2021-09-20 14_17_44-[WS-803] Menu styling inconsistent during browser resize - Prodigy JIRA.png

Like Robert Horan likes this

That seems strange that it's not in your list of existing labels. Why are you doing it that way? Why not use a project picker custom field and call it Project Assignee or something, for example we have one called 'Implementation Team' for Planned Change issue types where they're raised in project A but done by the Team that lives in project B.

Hi there. I think this is what I'm looking for, but I'm confused of how to trigger this rule from another. The checkbox says to allow other rules to trigger it, but what do I do on the rule that's supposed to be the trigger?

Not sure I'm asking that clearly, but I hope you get the gist! 

Hi,

You don't need to do anything special in the "trigger" rule. The action that this rule triggers should be an action that trigger the 2nd rule.

 

For example:

Rule 1# - if all tasks in a story are set to "DONE" > update story status to "QA"

Rule 2# - Whenever a story is moved to "QA" > assign the QA lead and send an email

 

Hope this makes sense

Like # people like this

There are two different forms of questions being asked in this overall thread we've been sent to. Both relate to rule triggering but they're different underlying questions/use cases. The distinction is in one scenario there would be a way to add an ACTION in a rule to call another rule vs the rule being capable of triggering because another rule took an action that made triggered some underlying event (which itself is a weird oddity in the first place that it doesn't just trigger by default)

 

(though it sounds like the answer to this question is : No it is not possible yet.)

Great inspiration in this thread.

 

I wanted to create 4 stages to a process due to the volume of sub tasks that needed to be raised, so each time a primary ticket was raised you had to manually push through the workflow to have the sub tasks created.

I added a custom field (called Stage) and when the value change the automation ran.

If the value was x, then the relative sub tasks were created. Once they ran, the automation changed the value to y and the relative sub tasks were related, and so on.

Getting the first part of the 'if' to change the value and then as the value changed the automation run.  Very smooth.  25 sub tasks created in minutes and all automated!

I did find out (the hard way) to check your logic.  I initially caused a problem when 2000+ tickets were created in a loop!  Thank goodness for test projects and delete permissions!

Update:  I've not got the post function changing the value 'Stage' which then prompts the next automation to run, so all sub tasks are fully automated.  (I do love a good automation!) :) 

Not sure if this can still help.
But I created a rule to add a comment, then another rule to be based off that comment text.
 
Rule 1;
SLA 1 hour after 1 hour > Add Comment "You have not responded to this in an hour"

Rule 2;
Comment Added > IF Comment Contains Text "You have not responded to this in an hour" > Trigger alert through Webhook.

Risks - If someone adds this text specifically, it will raise an alert. So you have to make it unique as possible. Potentially you can put Symbols at the start and end like !"You have not responded to this in an hour"!
You just have to trust people in your company not triggering the alert themselves...

I find the trigger thing bizarre, especially when the 'when' can be issue updated/created. you'd think well, surely my trigger should ALWAYS trigger the rule to run, whether the tick box is ticked or not.

Hi

I think  might not be understanding this correctly. Let me describe my scenario. 

I have some fields that are populated from data available in other fields on a manual trigger by the user. 

 

Now I want to create another rule that will do the same but not on manual trigger but based on 

1. Transition to a certain Status

2. Edit of an issue field (one of the custom fields that I am using as input for populating the others fields in manually triggered rule.

 

Is it possible to execute the manually triggered rule based on the triggers mentioned above in 1. and 2. 

Or do I need to recreate the same rule but with different trigger which are transition trigger and Issue field update trigger.

I haven't found an action to trigger one rule from another rule. Please could you help me understand, how does the "Allow rule trigger" checkbox should imply?

I have the same question.  I have automated rules for transitions.  Say #1 is Manually updated tasks and subtaks, and then  #2 Close Epic if all tasks/subtaks done (this is done during transitions)

I manually run #1, but I want it to kick of #2 after it finishes #1.  How do I do that?  What do I do in #1 to get it to go to #2 

Like Heather Arbiter likes this

It's a little clumsy but I accidentally stumbled across this solution: Add to the workflow a same status loop that triggers the manual automation. Then you can push the issue through that status in your second automation which will trigger the first one. (Allow rule trigger checkbox was not required).

It isn't ideal though. Allowing an automation to trigger another one seems pretty desirable as the alternative if you want to have an automation that can also be triggered manually you seem to just have to duplicate and maintain two automations. 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Apps & Integrations

🍻🍂Apptoberfest Update: Upcoming Virtual Events 🎉

Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...

394 views 3 17
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you