Why are my clone issues not linking to my trigger issue in my automation?

[Jeremi Nilsson]

I have an automation rule that makes a task every time an epic is moved to in progress as shown, 

I want it to link the task created to the epic but i can't seem to get the link to work. I have tried many combinations in the And: Link Issue to rule and it says it passes fine in the log (as shown below) 

but the epic link doesn't populate as shown below,

Am i missing something in the automation? I want the Epic link to populate on the task with the Epic that triggered the automation. Any suggestions on a fix? Thank you.

[Luka Hummel - codefortynine · Accepted solution]

Hi @Jeremi Nilsson

I'm Luka from codefortynine.

To link the trigger issue to the newly cloned issue, you either need to use a FOR EACH branch for the Most recently created issue and then link the issue to the Trigger issue or

you can just link the issue to the Most recently created issue. This of course would break if multiple issues are created in your automation.

If you need to clone more data, like custom fields, from your source issues or notice that your clone breaks when making changes, I want to suggest using our Deep Clone for Jira app. You can also use a Deep Clone preset as a workflow post function and use looping transitions to have it trigger in an automation.

[Jeremi Nilsson]

The link says it was successful but the epic link is still not populated.

[Luka Hummel - codefortynine]

Ahh! I misunderstood your question. The Epic Link isn't an issue link but another field value.

You can edit the Epic Link/Parent field when cloning under More options like this:

{
"fields": {
"parent": { "key": "{{issue.key}}" }
}
}

[Jeremi Nilsson]

That worked, Thank you a ton!