Auto Link Epic to Newly Created Issue

[Christopher D_Auria]

Hi all, 

I am trying to create an automation rule that automatically links the newly created ticket to an epic for a new JSM project. In this project, each epic will represent a different customer project that my team is working on. My current rule is below. I am trying to use the reporter account ID to match the new issue to another that the user has made before and then copy that parent link to the new ticket. Do you guys have suggestions to make this method work or another method that would work better? 

Other factors that may be relevant or could be used: 

- I have a form for the customer to fill in that has a field for them to put the project name in which would be a similar name to the Epic name

- I can't put a parent field for the customer to fill out as that would allow them to see other customer projects. 

[Trudy Claspill]

Hello @Christopher D_Auria 

Welcome to the Atlassian community.

What is the output in the Audit Log for execution of this rule?

You are looking for another issue created by the same person, but in the CS project? In what project is the trigger issue for this rule created? If it is not the same project, have you set the rule scope to include both the trigger issue project and the CS project?

[Christopher D_Auria]

Hi @Trudy Claspill

Thanks for the welcome! 

I am looking for issues created by the same person in the same "CS" project. The lookup issues is working as expected. The main part I am struggling with is being able to take the same parent and link it to the newly created ticket. 

Lower in the rule, I have an else block which is performing as it should. But the audit log is stating that the newly created ticket does not match the first if statement which is supposed to do the automatic linking. 

[Trudy Claspill]

Thank you for that additional information. 

It appears that these steps align with these messages. Do you concur?

Can you show us the details of the Create Variable action?

Can you add a Log action after the Create Variable action, to print to the log field the value of {{LookupParent}}? Then try running the rule again and share the audit log with us.