-
Bug
-
Resolution: Duplicate
-
Low
-
Severity 3 - Minor
Issue Summary
When a variable is created only inside IF/ELSE Block or in a Branch then the variable is not accessible anywhere in Automation apart from the Branch.
At the same time, if you create one Global Variable (after the trigger or before IF/ELSE block or branch) and then other variables created inside IF/ELSE Block or in a Branch will be accessible anywhere.
Steps to Reproduce
- Create a Automation,
- Add If/Else Block or other Branch , create variable inside If/Else block
- Add Log action within If/Else block to Print Variable created in If/else block. It works fine.
- Now Add Log action outside If/Else block to Print Variable created in If/else block. It doesn't work.
Expected Results
Variables should be accessible in all places in the rule.
Actual Results
Variable is not accessible.
Workaround
- Create Global Variable right after the trigger or before the IF/ELSE block or branch like below.
- Then all variables will be accessible.
- duplicates
-
AUTO-154 Automation: Ability to use variable outside of a block - variable is not updated on main branch if created inside an if/else or branch block
- Gathering Interest
- is related to
-
- Gathering Interest
[AUTO-1260] Variable created inside IF Block or Branch is not accessible outside of a block , if there is no variable created globally (after trigger) in Automation
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Hi team, Dan here from Automation Platform,
I was able to replicate the described behavior and log after the if-condition a variable created inside the if-condition (if there was another global variable created first).
Regarding variables behavior, we have to distinguish two use cases here:
- Inline branches: if-conditions and inline branches that are executed once-and-only-once (e.g. on Parent, on Current Issue, etc.) run in-line (synchronously). This a decision made a long time ago for optimisation purposes.
- Branches that are executed on more than one issue (e.g. JQL, linked issues, etc.) are run in parallel and asynchronously. There is no guarantee of when the branch will finish, until right up to the end of the rule and because of that whatever happens inside these branches (e.g. new variable creation) remains so, except for any issue updates, web requests, etc.
In this original community post you can find more details: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Create-variable-New-component/ba-p/1448118
Had a discussion with our team and this seems indeed like a confusing behavior that should only be happening for inline-branches. Moving to gathering impact.
Thank you,
Dan
| Labels | New: jsw-s13 |
AUTO-154