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; } } }

Automation to clone an Epic with child issues and their subtasks

Bahia Mezraoui

Hello JIRA community!

I have a question regarding the cloning of an Epic when it contains child issues (which also have sub-tasks). I'm currently trying to create a rule for it but can only succeed at the first layer, meaning the cloning of the Epic itself.

Here are the 2 attempts I've made so far:

Automation for Epic cloning.png

Automation for Epic cloning2.png
For this second rule, I've indicated first level of cloning as Epic then Task then Sub-task that is why I've added the action 3 times.

I think I'm missing a step (or a few), any guidance would be much appreciated

Thank you!

Accepted answers

All comments

Dexter de Vera

Hi @Bahia Mezraoui ,

Check this other post it maybe useful

https://community.atlassian.com/t5/Jira-Software-questions/How-to-clone-the-whole-Epic-and-child-issues-included-in-the/qaq-p/187196

Thibaut Subra _Elements_

Hello @Bahia Mezraoui

Welcome to the Atlassian Community!

I see that you find yourself needing to copy Epics along with their entire issue tree, know that we developed an app called Copy & Sync and it’s just what you need!

We've prepared a helpful "How-to" guide that walks you through the process step-by-step.

Moreover, as you're using Automation, know that you can trigger a recipe directly through Automation using our API with just one simple rule.

If you have any questions or need assistance, feel free to reach out to me anytime.

I'm here to help!

Luka Hummel - codefortynine

Hi @Bahia Mezraoui and welcome to the community!

While you can automate this, the set-up is quite tedious and the automation rule can break quickly if there are any changes. If you are willing to use a third-party app, our Deep Clone for Jira can quickly clone whole issue hierarchies (Initiatives → Epics → Tasks/Stories → Subtasks) with its Epic/Tree Clone feature.

Bahia Mezraoui

Hi @Luka Hummel - codefortynine , thank you for answer I will look into this app

Bahia Mezraoui

Hello @Thibaut Subra _Elements_ thank you for sharing, I will check it out

Bahia Mezraoui

Hi @Dexter de Vera , I did see this question but it only give part of the answer to mine. Thanks for sharing!

Bahia Mezraoui

Hi again @Luka Hummel - codefortynine just out of curiosity, I know you mention that setting up the automation would be quite tedious but can you share an overview of the steps if you have an idea? Many thanks!

Luka Hummel - codefortynine

Hi @Bahia Mezraoui

I will try to give a basic overview of the steps. These are of course more complicated if you need additional field values copied or need to create more issue links.

Clone Epic
FOR EACH Most recently newly created issue (Epic): Create issues and add parent field with Advanced fields under More options. {"fields": {"parent": { "key": "{{issue.key}}" }}}
FOR EACH All created issues: Create Subtasks

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-work-management