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
Within the last week, I was able to drag and drop branch rules so that one branch rule is within another (see below).
Now, I can't drag and drop branch rules at all within the same automation. Anyone know if this is a bug or if something with the functionality that changed? Clicking "Add component" where I want the branch rule to appear (beneath the "Create a new Task" action doesn't list branching as an option, but I've been able to get around this in the past by dragging and dropping branch rules.
Hi @dowens1 -- Welcome to the Atlassian Community!
I have seen several posts about this behavior before, and I hypothesize it is an accident/defect that it works sometimes. If nested branches were intended to be supported they would be in the documentation...probably with several articles written describing use cases and limits. I'd welcome input from the automation dev team if this is intended to work.
And for the rule you have shown, technically the "branch" on most recently created issue gets converted to in-line code. Branches on more than one issue get run in parallel and asynchronously, and so I would guess performance issues and potential errors could be why this structure may not be supported.
Apologies in advance for the long explanation :^)
For branches on one-and-only-one issue (e.g. last created, parent epic, current issue) when the rule gets parsed and run, the rule steps runs in the order you see them. Essentially the code is "in-lined" with the loop "unrolled", in dev-speak. This has been confirmed by a few Atlassian folks in community posts.
However, when a branch is/could be on more than one issue (e.g. for sub-tasks, JQL, related issues, etc.) each issue/value gets run separately and in parallel for the branch steps. And there is no guarantee of the processing order or even that the last one will finish until the very end of the rule's other steps.
Here's an example:
The current, actual order of processing will be:
I believe there is a suggestion to add an option to finish such a branch prior to continuing, similar to what is available for the Send web request action.