You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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
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?
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.
Your thoughts ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I figured out using labels and triggers to call trigger a child rule, it is achieving the desired result for now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.