Use JIRA automation to create stories and sub task cloned with the Epic

[Lily Roy]

I am trying to create an automation in Jira, in that when a new epic gets created (with that new Epic) the stories and their sub-tasks into a new Epic ready to be prioritized in the backlog may be like place holder.

So that every time no need to start the story from scratch.  

[Mark Chaimungkalanont]

Hey there! You should be able to create a rule that:

1. Triggers on issue creation
2. Condition that checks the issue type for an "Epic"
3. A series of actions to create your default issues
4. A "Issue branch" that loops over the the list of created issues
   1. Within that branch you can create subtasks for those created issues

Good luck!

[Antonio Rivera]

Hello @Lily Roy

Were you able to solve this? I'm looking to implement the exact same automation. 

[Lily Roy]

Hi  There,
Nope its not working ,if possible looking for clone (as automation is not working)

[Antonio Rivera]

What I came up with was to create a placeholder (epic) with all stories within and automate a duplicate of it. But in my case I haven't been able to automate the assignee and other fields values correctly. 

I used Frother's comment on this question to create the automation rule. 

Hope it helps!

[Marlene Kegel - codefortynine]

If you are open to work with a Marketplace app, you can try Deep Clone for Jira (I am the product manager of this app). With the Epic/Tree Clone you can clone entire issue trees and keep their hierarchy.

Deep Clone for Jira is more flexible than Jira Automation in some areas when it comes to to configure clone settings.

It's also possible to integrate Deep Clone with Jira Automation.

[Antonio Rivera]

Hello @Lily Roy

I was able to figure out a workaround to kind of have a template for all the stories within an epic. What I did was to create the epic to be cloned along with all the  stories in it and keep it on the backlog so team members can go directly to it and clone it.

The rule configuration is: 

To ensure all new epics contain all required stories team members must: 

1. Go to the Epic Template

2. Execute the manual automation rule

3. Move the cloned epic with all its stories to the team member's board. 

4. Update all 

Hope this helps you solve your situation. If anybody else have suggestions on how to improve this, please comment and tag me to review and test on our boards. 

Thanks!