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
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
I have three custom fields, each of which is filled in automatically when creating an issue using automated rules with certain values. It is fundamentally important for me to set up a strict order of execution of these automated rules using Webhook. The order of the rules should be as follows: first, RULE 1 is executed, then RULE 2 is executed, and only after successful execution of RULE 2, RULE 3 is executed. According to my knowledge, I understand that each rule should have an action "Send web request" and another one should be created. an automated rule triggered by Incoming webhook. Can someone tell me how to implement your plan?
For automation for Jira, the only way I know to enforce the order of triggering for a set of rules is to:
For #1, that means creating conditions in your rule to make updates which lead to a trigger firing. For example, if Rule-A updates an issue's fields, Rule-B's trigger checks for the update to the field of interest.
Of note: for such a use case it may be helpful to use the Re-fetch action after the trigger in the downstream rules. This will reload the data and reduce the chance of timing issues where the issue data has not caught up with the prior changes.
I have the same situation. I do have the "Allow rule trigger" checked on my second rule. But where do I indicate which rule it should follow? Can you only do this by webhooks?
If I want to set the webhook, how do I know or create the webhook?
I would guess that I need the URL for "running" the automation, not just the URL for the edit automation page.
I'm on Cloud version. Will I have access to this?
That is not how the option "Allow Rule Trigger" works...When you have multiple rules and the actions of one rule could trigger another, you may enable Allow Rule Trigger in the "downstream" rules of the earlier one(s).
The use case of using webhook to chain/trigger rules is only needed when your rules do not create conditions which can be detected by other rules. That seems like an edge-case to me, and often this can be solved be re-considering your rule designs.
If you are having a specific problem with rule triggering, please create a new question. Otherwise only the people following this old thread will see what you are asking. With your new question, please include the following for context:
Well done! That is often a better way to go, when possible, as it reduces some timing issues.
The caveat is any branches in a rule: branches which could run on more than one issue are run asynchronously and in parallel. And so if you need the results of processing earlier in the rule to roll-up some value, that is not possible in one rule with a multi-issue branch.