Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,362,731
Community Members
 
Community Events
168
Community Groups

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

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.  

2 answers

1 accepted

2 votes
Answer accepted
Alexis Robert Community Leader Jun 09, 2021

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) : 

 

Screenshot 2021-06-09 at 14.11.47.png

Screenshot 2021-06-09 at 14.12.04.png

 

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 :

Screenshot 2021-06-09 at 14.14.14.png

Screenshot 2021-06-09 at 14.14.27.png

 

Screenshot 2021-06-09 at 14.14.47.png

 

Let me know if this helps, 

 

--Alexis

Fantastic.  That works, thanks for your help.

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)?

 image.png

Did you solve your problem?

Hi,

 

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events