Automation for Jira - Clone Epic, Story and Sub-tasks

[Nicola Greene]

Ideally I am trying to create an automated rule in jira, such that when an epic (with certain labels) transitions to Done, it clones the epic, the stories and their sub-tasks into a new Epic ready to be prioritised in the backlog. 

If this is not possible, then my option 2 is to have an automated rule that where a story (with certain labels) transitions to Done, it clones the story and its sub-tasks into a new story within the same epic.  

[Alexis Robert · Accepted solution]

Hi @Nicola Greene , 

this is actually a little complicated to do, but I found a way using 2 rules and labels to trigger copies.

First, you'll need to setup a rule that will clone the Epic, and "tag" the issue in this Epic with a temporary label (this way we now what issues to clone in the second step). We will also store the new Epic issue key in a temporary link for those stories.

It looks like this (first screenshot has the details of the Clone action, second one has the details for the Edit Issue action) : 

Then, the second rule will identify the Stories that we need to clone (and also clone their subtasks). Again the screenshots will show the details for each action :

Let me know if this helps, 

--Alexis

[Nicola Greene]

Fantastic.  That works, thanks for your help.

[Nicola Greene]

I'm getting a few errors on this, it seems to be the epic link part.  What is typed in the Epic Link box above (I can't see the full text in the picture)?

 

[Ye Fung Tchen]

Did you solve your problem?

[Diego Quesada]

Hi,

I have created the two rules, but only one is executed. Do you know, what is the root cause?

[Nacho García-Robledo]

Same for me, first automatism works but the second is not triggered even the label has changed.

If I do it manually it kicks in, but it does not make sense for this case.