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.
I've found some curious behaviour when trying to create a variable in a Jira automation routine. If I create a variable in a branch line so:
{{cake}} was able to be recalled in the email within that branch ("cakecake"), but isn't able to be recalled outside of that branch (the one called "middle").
While trying to debug this behaviour I discovered by chance that by adding a new variable before the first branch somehow resulted in the expected behaviour. ie the automation below worked and the value of {{cake}} was able to be recalled in the email "middle"
Not sure if this is a bug in the way the platform handles variable creation, or I think in my troubleshooting googling i read something somewhere that branches may be processed in parallel, meaning that perhaps the email "middle" is being sent before the branch that creates {{cake}} is executed?
based on what I've read, variables created in branches only live within branches (you lose them when you move outside the branch) but variables created at the top level are accessible during branching, so what you are seeing is expected behavior