nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Clone entire project with epics

Talha Shah

I have a template project with many default epics that I would like to be cloned in new projects I create. I need these new epics to be children of the new project with no reference to the template it was created from. How could I set up my Jira automation to loop through all epics in my template project and to recreate those epics in a new project. I would like to copy all attributes of the epic as well.

I'm really looking to accomplish this through an automation and am not interested in any marketplace solutions

Accepted answers

Mark Segall

Hi @Talha Shah - How many epics and children are we talking about? Automation may not be the best approach for this because you could run into limitations on how many issues and/or throttling if the process takes too long to complete.

Additionally, because automation is working in a threaded model, there's no way to force it to clone issues in the same order so if your expectation is that they also come over in a logical order, you'll be disappointed.

You may want to invest in a marketplace app for this.

All comments

Mark Segall

You may want to invest in a marketplace app for this.

Trudy P Claspill

Another alternative is to keep the information for all the "template" issues in a CSV form, and using the External System Import from CSV to create the issues in the new project.

https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/

Talha Shah

Hey Mark thanks for the reply. Our issue count seem to be comfortably within the throttle limit and order is not important so I've managed to setup our automation rules to complete a deep clone without an app

Florian Bauer

Hey @Talha Shah

you can consider your template-Epic as a process template if you want to repeat it multiple times. Then your epic is a process because recurring projects are processes!

Flower - Process Automation clones your Jira epics as repeatable processes, including all issues, links, and structures.

Here is how to clone a epic as a process.

Happy automating,

Florian

Michael Da Costa

hey @Talha Shah could i ask how you managed to have your automation rule loop through all epics please.

I have the same use case - i can clone individual epics (and children) to a new project but cant manage to loop through all the epics in my project!

Any help much appreciated

Thanks

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation