Automation help: Can I create issue links between brand new issues created by the same rule?

Question

Hello Atlassian Community!

Jira Cloud administrator here. I have a complex request from an end user to implement a new automation:

* The automation needs to create a new Epic, as well as 10 Stories

* Those Stories need to be child issues of that Epic

* Some of the Stories need to have issue links with each other, i.e. Story #2 needs a 'depends on' issue link with Story #10

I'll building this using default Jira Global Automations.

The Branch Rule/Related Issues function does allow for issue linking between the trigger issue and the most recently created issue, and you can set the Parent to be the current issue or the trigger issue. So none of those options give me what I need.

So my dilemma is whether or not I can create an issue link/parent relationships between the child Story and the Epic within the same automation rule, and if I can create issue links between brand new issues created in the same automation rule, too. I can create the issue in separate automation rules, but then I don't have a good way to reference back to the issues.

Anyone built anything similar to this? Do I need to use a third-party app? Am I attempting to build something that's impossible to implement?

Thanks in advance!

Bill Sheboy · Answer

Hi @Cory Beaudoin

This question has been asked a few times before in the community, and if you search you may find the details of the discussions / limitations / solutions attempted.

Essentially, if your rule has no branches to create issues, the key of each created issue could be saved with Create Variable, and then those variables could be used to add links...one by one.  Rules like this are sometimes limited by the maximum rule size of 65 components.

Kind regards,
Bill

Trudy P Claspill · Answer

Hello @Cory Beaudoin

Whenever asking for help with an Automation Rule it will help us help you if you show us the rule you have constructed.

It is possible to create a parent Epic issue and its child issues in the same rule, and get the Parent field in the child issues set to the Epic created in the same rule. Seeing the structure or your rule will enable us to advise you specifically how to implement that.

Creating generic issue links between the child issues may be a bit more complicated. Again if we see the structure of your rule we may be able to offer advice.