Automation to clone an epic that is not the issue triggering the automation?

[Jenn Sherman]

When an epic is created and that epic has fields that meet certain conditions, I want a "template epic" (that already exists in the project) to be cloned.  Any ideas on how to do this?   Here is the start of my automation:

When issue created

Issue type = Epic

custom field 1 is not empty

if: matches (followed by some JQL)

What I want to happen next is I want existing issue PB-417 (an epic with children) to be cloned.

[Alex Koxaras _Relational_]

Hi @Jenn Sherman 

Try the following rule, but replace the IF statement (field) with yours, as well as the issue key with yours. Let me know if this is what you wanted to achieve.

[Bill Sheboy]

Hi @Alex Koxaras _Relational_ 

What do you think about splitting the clone operation, to clone the template epic first and then clone the child issue?  In that way, the child issues can be correctly linked to the cloned parent epic, using {{createdIssue.key}}

As built, I do not believe that rule's clone action will re-map the linkages, parent to children.

Kind regards,
Bill

[Alex Koxaras _Relational_]

@Bill Sheboy indeed my friend! The children are not bind on the new epic and instead are linked to the original issue.

[Alex Koxaras _Relational_]

@Jenn Sherman I've got a question:

Say a user creates an Epic issue. You want this rule, even if the new issue an Epic, to clone nonetheless the PB-417 with its subissues? To my understanding perhaps you want to copy all values from PB-417 to the new issue AND close PB-417's subissues to the new epic. Am I right?

[Francisco Gomez Balastegui]

Hi, you can do this with ScriptRunner