Most Recent created issue key not found in automation

[Rai Warbasse]

Using Jira Version 8.22.1 project automation

The Setup:

A 'story' Issue contains a linked 'test' issue of "tested by"

When the test issue transitions to a fail, it triggers a transition on the story issue which triggers this automation flow.

When this automation flow is triggered, I create a 'defect' issue using a current issue branch and link the defect as blocking to the story.

I then have a second branch "for linked issues", to the story, which targets the test issue.

The Problem:

I am attempting to link the test issue to the defect issue by using the 'most recently created issue' from the 'link issues' action, but the issue key of the created defect issue can't be found; however, it is in the log output.

There are several articles similar to this but none of the solutions work.

LOG OUTPUT:

[Bill Sheboy · Accepted solution]

Hi @Rai Warbasse 

I believe you are seeing this defect/symptom where the {{createdIssue}} smart value is not visible to the scope outside of an if/else or branch in which the issue was created: https://jira.atlassian.com/browse/AUTO-154

Without seeing your entire automation rule, my suggestion would be to consider how you might restructure the rule so the create issue action is at the same scope where you need the {{createdIssue}} smart value.  Please post an image of your entire rule if you want ideas to help with that.

Kind regards,
Bill

[Rai Warbasse]

Thank you for that but it is contained with a single 'if' rule. Here is the whole view:

[Bill Sheboy]

I do not believe you need the For Current Issue branch as it is just nesting down from the trigger issue.  Instead you can just reference {{issue}} or {{triggerIssue}} as needed. 

Please try removing that branch to see if the {{createdIssue}} smart value becomes more visible to the branch below it.

[Rai Warbasse]

Bill, you are a savior. That was the issue. removing the initial branch fixed it.

[Bill Sheboy]

I am glad to learn that helped.

I find this symptom/defect curious as my understanding was that branches on one-and-only-one thing (e.g., branch to current issue) get converted to in-line code, as if the branch did not exist.  Compare that to branches which could be on more than one thing (e.g., linked issues, JQL, etc.) which get run in parallel and asynchronously, in separate processes.  I guess the "branch scoping" rules outweigh the in-line stuff for this symptom.