Linking tickets created using branch function

[Raghu Mani]

Following this https://community.atlassian.com/t5/Jira-Software-questions/Create-a-custom-list-object-to-loop-through-Jira-Automation/qaq-p/2171480

I have built a rule for my use case

The trigger is when the issue transitioned from Waiting for approval to Waiting for support 

Request type = New joiner

The custom field(Name of the field is Application software)  is not empty

The tickets are getting created as expected, but there is no way I can do the below functions because I can not find the recently created issues using the branch as I am already inside the branch. 



@Nathan Phillip Brink 

[Nathan Phillip Brink · Accepted solution]

Hello,

The documentation for create issue is at https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-issue . It states “Select More options to display additional fields for advanced field editing. ”. I think you want to use that option. See this topic: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/ . Many of the things you are trying to do after ticket creation can be done by using the advanced JSON during ticket creation.

For example, you can link the issue with issuelinks: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Linking-issues

If you use the approach above, you will not need as many follow-up actions.

However, the above is very advanced. It might be difficult to debug even if it could be the optimal solution. Also, I am not sure if every feature is available.

Please see this answer which describes the createdIssue smart value. You can simply use createdIssue in your same branch to reference your created issue. This is more reliable than “recent” because “recent” introduces a race condition—your automation might perform some action on an issue which another user just created instead of the issue which your rule created.