Automation to Clone an epic with all the child issues

Mickey Somra

Can anyone assist in identifying the issue to fix with the Automation Cloning?

We're using the Jira Cloud and I'm looking to clone an Epic and all the child issues from one Epic to the new/cloned epic.

 

I am not going to get approval for an external app as I was directed to "Automation"..

 

Project Type: Team-managed software

Automation Rule

Image 1: Overview

Image 2: For: Children

Image 3: Then: Clone issue into

 

Example Epic (I have an epic with much more issues but I figured starting with something small would help)

 

When the rule runs, this is the generated message:

Trudy P Claspill

Hello @Mickey Somra 

Welcome to the Atlassian community.

The issue has to do with the special nature of the Issues Linked trigger.

With this trigger there are two issues involved; the two issues being linked.

The rule has to determine which one is considered the trigger issue, to provide context for how the rest of the rule will execute.

It does this by looking at the link created between the issues and identifying one as the "source" of the link and the other as the "destination" of the link. The one determined to be the "source" will be considered the issue that triggered the rule.

To determine the source and destination issue in the link the rule looks at how the link between them is configured. Each link type has an Inward Description and an Outward Description. For the default Cloners link they are:

Inward Description	Outward Description
is cloned by	clones

The trigger issue will be the one that falls under the Inward Description part of the link relationship.

When you look at the links section under SAP-171 does it say...

Is Clone By
-- SAP-206

...or...

Clones
-- SAP-206

 

The rule should run for SAP-206 when it falls under the heading "Is Cloned By" as you view SAP-171. This is supported by the messages shown in the audit log identifying SAP-206 as the "source" issue.

In that case the rule proceeds under the context that SAP-206 is the triggering issue.

SAP-206 is the new issue you created by cloning SAP-171, therefore SAP-206 has no children yet. So the Branch has no child issues to reference.

For your Branch I recommend that you instead use the Related Issue / JQL option.

That will retrieve all the child issues of the Epic that was cloned.