Automation: issue created in a different project with the parent project

[Daniel Caspy]

Trying to create a new issue for an epic, but I want that issue in a different project. The problem is it won't associate the issue with the epic.

[John Funk · Accepted solution]

Hi Daniel - Welcome to the Atlassian Community!

What is the trigger that causes this automation to fire? Is it something that happens with the Epic and you want to then create another issue (in a different project) with the trigger issue to be the parent? 

If that's the case then the Epic Link field should use:

{{triggerIssue.key}}

[Daniel Caspy]

We used to trigger automation through components. I tried to trigger this one through the manual trigger trigger from within the epic. Ideally, I'm creating the epic and at some point, in time I want to create these tasks for the other project.

[John Funk]

It's really going to depend then on how it gets triggered. If you create the Epic and then want the children to get created immediately OR if a value changes on the Epic (field or status based on a transition), then the above code works. If it is something else, we would need more specifics. 

[Daniel Caspy]

I'm going for the latter really. In which case I'm using the manual trigger. The problem is that the tasks aren't getting associated with the epic link.

[Kelly Arrey]

How does the automation rule know which epic to associate the tasks with? 

[John Funk]

Yep - that’s the question.

[Daniel Caspy]

So that's my question. What can I do so the automation knows to associate that epic? I tried using {{issue.Epic Link}} and starting the automation from within the epic with the manual rules. Should I create a field that exists within that epic? I feel the issue is that the the new tasks are being created in a different project.

[John Funk]

So, can you lay out your scenario? What issue are you on when you do the manual execution? And what do you expect to happen? 

[Daniel Caspy]

A project manager wants the epic to exist within their own project but wants the tasks to exist in multiple other projects. 

I don't want them to manually create the task, and it is something that repeats itself with every epic. I want to create automation to open tasks in different projects with specific fields and such. 

I expect the tasks to be opened with automation in the projects they need to be in + have the correct epic link.

[John Funk]

So the project manager is in an Epic, then clicks on the execution of a manual automation rule, and it creates the children stories identified in the rule (regardless of the project). Is that correct? 

If so, what I showed you above is what you should do for the Epic Link field in the children getting created. 

[Daniel Caspy]

@John Funk It worked perfectly. Thank you so much. I didn't understand I needed to put it in the epic link. Much appriciated.

[John Funk]

Great! You are very welcome. Sorry for not being more clear to begin with. 

[Daniel Caspy]

Think nothing of it. You've helped immensely.