Clone EPIC & Stories to New Epic and link New Stories via Automation

[Chandan Bhome]

I created this Automation rule, however when I clone the Epic it not keeping the child stories. Rather the child stories are sitting in the backlog. @Mark Segall 

[Michael Ludvigson]

i seem to have the same issue.  its cloning the epic and the stories under the epic, but not attaching the cloned stories to the cloned epic.  it's leaving them in the backlog.  what am i missing?

[Michael Ludvigson]

please disregard.  I figured out I had the wrong clone issue.  I changed it to match your screenshot to clone stories and it's working perfectly now.  ty.

[Chandan Bhome]

Thanks @Mark Segall 

I now see two epics being created. Once has the user stories linked to it and the other does not

[Chandan Bhome]

[Mark Segall]

Hi @Chandan Bhome 

So your variable needs to be the issue key of the issue just created in the step above.  The smart value should be this:

{{createdIssue}}

 For your Create issue, you'll need to add the Epic Link or Parent field depending upon whether your project is a company or team managed project respectively.  (If you don't see Epic Link as an option, you're a team managed project).  Once you've added the field, you'll set it to this:

{{varEpic}}

[Mark Segall]

@Chandan Bhome - You're close.  The variable should include the curly braces:

{{createdIssue}}

[Mark Segall]

Looking at your screenshot, I don't see how there are two Epics being created.  It looks like the clone action (which creates the Epic) only creates one issue and then the create issue (which creates the child issues) creates two issues.  

This wouldn't create a duplicate Epic, but one thing I do see is that you have Epic Link captured on the Clone Issue action which should not require this as Epics do not make use of the Epic Link field.

[Chandan Bhome]

Removed the Epic link, however, still clone epic 1 with no child issues and clone epic - 2 with  child issues.

[Mark Segall]

Do you happen to have a second rule executing?  Your last screenshot of the rule log looks like this rule is executing properly which makes me think that there may be a collision happening with a second rule.

[Chandan Bhome]

No, I don't, this is the only rule that is executing. Surprisingly the audit log does not show clone epic 1 at all. 

The only explanation I can think of is when I click "clone" two actions are triggered. One with the automation rule and one with my action of clicking "clone"

[Mark Segall]

when I click "clone"

Are you cloning the Epic AND running the automation?  If so, you shouldn't need to do that.  Since this is a rule configured to trigger manually, you should be able to simply click Actions >> Clone Epic with Child Issues

[Chandan Bhome]

Success, thank you @Mark Segall