How to: When Epic is cloned→ clone child tickets

[Svenja Diester]

I want to create an automation that clones an Epic and all its child issues (stories and subtasks).

So far, I have managed to clone the Epic and its corresponding story, but not the subtasks. Additionally, the links between the Epic and the story are not cloned either. I have adopted an automation from a previous post, which looks like this:

However, I always receive this error message while attempting to execute it (See below)

It is important to me that the cloned issues are connected to each other. This means:

I clone Epic 1, which is associated with Story 1. Subtask 1 is a child issue of Story 1. I want to ensure that the connection between Epic 1, Story 1, and Subtask 1 remains intact. Furthermore, I want to get Epic 2, which is associated with Story 2, and Subtask 2, which is a child issue of Story 2.

How can I achieve this?

[Thibaut Subra _Elements_]

Hi @Svenja Diester 

If you seek an easy way to do it, I suggest to try our Copy & Sync app.

You can copy EPICs and all child issues (stories as well as subtasks), keep a connection between them (synchronize them if needed) and you can do it all by triggering the recipe directly from Automation using our API (if there are any conditions to the copy).

Happy to help if you want, our app is free under 10 users and we have a 30-Day trial policy.

Let me know!

Regards

[Luka Hummel - codefortynine]

Hi @Svenja Diester

If you are still struggling with creating a Jira automation and are willing to use a third-party app our Deep Clone for Jira can clone whole issue hierarchies, including Epics > Tasks/Stories > Subtasks, with our Epic/Tree Clone feature.

The app is free for up to 10 users and you can try the app for free for 30 days.

[Trudy Claspill]

Hello @Svenja Diester 

Are you working with issues in a Team Managed project or a Company Managed project?

For a Company Managed project take a look at the answer from @Alexis Robert on this post.

[Svenja Diester]

Hi @Trudy Claspill 

I'm working on a Company Managed Project. However, it seems that this approach is only applicable to Epics that are already completed. In my case, the Epics are still in progress. Additionally, there are many other individuals creating tickets, so the "most recently created issues" part doesn't work effectively, as it would also clone tickets from my colleagues. Therefore, this solution won't be helpful for me. Nonetheless, thank you anyway.