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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,534
Community Members
 
Community Events
176
Community Groups

Creating a rule that will run other rules

Hi, 

New to Jira autmation & rules. 

I want to create rules that I can reuse, by calling these from a "parent" rule. but I can't seem to find any good explanations / examples. 

I can see how to create a "child" rule without a trigger, or which is the correct trigger, as I only want the child rule to run when called by the parent rule. 

How does one call a child rule from the parent I can't see which action to use. 

Thank you 

Greg

1 answer

Hi @Gregory Machin 

There isn't a trigger which "calls" another automation rule, but you could set the Parent Rule to make a unique modification on an Issue (eg. add Label, etc), which is the Trigger for the Child Rule to activate (eg. Field Value Changed Trigger).

To allow one rule to activate another - you also need to set this in the Rule Details section - ensure the checkbox "Allow rule trigger", "Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule" is checked / TRUE.

---

Could you provide some more detail in relation to this need if you'd like more specific instructions on how to set up these rules?

  • What does the parent rule do?
  • What does the child rule do?
  • When should the parent rule call the child rule?

Ste

Thank you Stephen for responding. 


The rule I have to remediated is triggered when a new issue is created, based on the content of the description, new tasks are created and linked to the initial issue, there as a fair amount of logic and actions in the current rule and it has hit the 65 limit.  My intention was to break it down into child rules, a rule for each type of task, eg tasks intended for Service Desk would all be under one rule, and all tasks for networks would be under another rule. 

  • What does the parent rule do?
    would be triggered on new issue, with logic to determine the required tasks that need to be creates. 
  • What does the child rule do?
    The child rule will do the work of creating the task or tasks based on the requirements. 
  • When should the parent rule call the child rule?
    When the appropriate logic has been triggered. 

 

Your thoughts ?



Hi @Gregory Machin 

Could you provide some specific details about the rule and how the Tasks are generated from the Parent, and linked back to it?

It doesn't need to be the whole rule, just a sample of it :)

To use separate rules, you'd need a method for the "Child Rule" to identify the parent and link back to it. Is there a unique parameter on each parent Issue that could be used for this?

Ste

Hi @Stephen Wright _Elabor8_  

I figured out using labels and triggers to call trigger a child rule, it is achieving the desired result for now.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events