JSM Automation Link to Epic problem

[John Funk]

Hey Everyone,

I have an automation rule I can't figure out. See the rule image below. Basically, I am firing a trigger based on new Epic getting created. Then I create another issue. Part of that issue creation links back to the Epic (using Trigger Issue) and that works fine. 

But now I need to create a second issue based on a combination of values in the first card created. So, I created a branch. It works fine and the second card gets created and copies down all of the values. 

However, the field for Epic Link in the second issue always throws and error that it can't find the parent. 

The field it is referring to is the Epic Link. Again, no matter what I put in there, I get the same error - whether is Copy from Current Issue, Copy from Trigger Issue, Copy from Parent Issue, Copy from Epic Issue.

[Yvan Martin]

Hi there,

Developer from Automation here.

You should be able to refer back to the original trigger issue by using copy from trigger issue on the field, or using a smart value on {{triggerIssue}}.

Your issue might be due to the particular fields and setup you have, if you are continuing to have problems then it's best to contact support since they can look into your instance configuration: https://support.atlassian.com/

This rule worked fine on my instance: 






Cheers.

[John Funk]

Hi Yvan - As noted in my original question, we have tried that and it still fails with the Parent error. 

[Walter Buggenhout]

Hey @John Funk,

Without having tried to simulate your rule, can't you store the Epic link in a variable before you branch your rule and use that to set the Epic link for your second task?

My guess is the problem is related to the fact that your creating the second issue while you are in the branch of the task you created. And that's not an epic or not the parent of the additional issue you're creating. 

[John Funk]

Hey Walter - thanks for the reply. I haven't used variables in automation before - do you have some same code for the Epic Link?

[Walter Buggenhout]

Hey @John Funk,

I think I managed to get there:

 

I created an epicLink variable while the automation is holding the Epic issue current and simply fetched the {{issue.key}} as smart value.

Then, to update the epic link of my newly created issue, I used the advanced options to update the Epic link field like this:

Then managed to run the rule successfully at least once 😅.

Hope this helps!

[John Funk]

Thanks! Will give it a whirl and let you know!

[John Funk]

I get this error:

[John Funk]

I ended up breaking the rule up into two separate rules.