I am currently using template Epics that contain multiple tasks and subtasks. I often need to clone these Epics, but I don’t want to clone all subtasks every time—only some of them based on the scope of the work. Right now I’m using the Deep Clone app, it can filter which subtasks to clone via JQL, which works, but I’m wondering if there are alternative approaches. Specifically, I’m looking for a way to: * Clone a template Epic and select which subtasks are included in the clone, * Or have a more user-friendly way than writing JQL each time to control which subtasks are cloned. Are there any built-in Jira features, automation rules, or other marketplace apps that allow cloning Epics with the ability to selectively include subtasks without relying on JQL filters every time? Thanks

Hi @Ahmet Fatih Ayyıldız , Cloning template Epics with selective subtasks isn't native in Jira Cloud Standard, as clone operations are all-or-nothing for hierarchies. For best choice, you can try out few apps below: 1. Clone Expert for Jira (Paid, free for instances with less than 10 users) * It lets you clone Epics/templates with hierarchy, then preview and edit issues before finalizing—selectively exclude subtasks by unchecking them in the preview dialog (no JQL needed). * Setup: Install from Marketplace > Clone from Epic view > Choose "Include subtasks" > Preview mode to pick/drop. 2. Easy Clone for Jira Cloud (Paid, free for instances with less than 10 users, but I think the pricing is lesser than the above one) * Deep clones Epics/subtasks while maintaining relationships. No direct selective UI, but pre-configure via templates or filters (less flexible than Clone Expert, but simpler if subtasks are grouped by labels). But, you can try the below guide but it is not ideal for interactive. You can try automation but it's limited as 100 runs per month: * Pre-tag subtasks in your template with labels (ex: "Core", "Optional1", "Optional2"). * Automation rule: Trigger "Issue cloned" (on Epic) -> Branch "For stories" -> Clone linked issues -> Condition: Label matches multi-select variable (prompt user for selection via form/email, but no direct UI. You can use Slack/Jira comment for input). You can refer to the below link: * Automation Basics Best, Peter

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

How to clone template Epics with ability to select specific subtasks?

Ahmet Fatih Ayyıldız

I am currently using template Epics that contain multiple tasks and subtasks. I often need to clone these Epics, but I don’t want to clone all subtasks every time—only some of them based on the scope of the work.

Right now I’m using the Deep Clone app, it can filter which subtasks to clone via JQL, which works, but I’m wondering if there are alternative approaches.

Specifically, I’m looking for a way to:

Clone a template Epic and select which subtasks are included in the clone,
Or have a more user-friendly way than writing JQL each time to control which subtasks are cloned.

Are there any built-in Jira features, automation rules, or other marketplace apps that allow cloning Epics with the ability to selectively include subtasks without relying on JQL filters every time?

Thanks

Accepted answers

Peter_DevSamurai

Hi @Ahmet Fatih Ayyıldız ,

Cloning template Epics with selective subtasks isn't native in Jira Cloud Standard, as clone operations are all-or-nothing for hierarchies. For best choice, you can try out few apps below:
1. Clone Expert for Jira (Paid, free for instances with less than 10 users)

It lets you clone Epics/templates with hierarchy, then preview and edit issues before finalizing—selectively exclude subtasks by unchecking them in the preview dialog (no JQL needed).
Setup: Install from Marketplace > Clone from Epic view > Choose "Include subtasks" > Preview mode to pick/drop.

2. Easy Clone for Jira Cloud (Paid, free for instances with less than 10 users, but I think the pricing is lesser than the above one)

Deep clones Epics/subtasks while maintaining relationships. No direct selective UI, but pre-configure via templates or filters (less flexible than Clone Expert, but simpler if subtasks are grouped by labels).

But, you can try the below guide but it is not ideal for interactive. You can try automation but it's limited as 100 runs per month:

Pre-tag subtasks in your template with labels (ex: "Core", "Optional1", "Optional2").
Automation rule: Trigger "Issue cloned" (on Epic) -> Branch "For stories" -> Clone linked issues -> Condition: Label matches multi-select variable (prompt user for selection via form/email, but no direct UI. You can use Slack/Jira comment for input).

You can refer to the below link:

Automation Basics

Best,

Peter

All comments

Tomislav Tobijas

Hey @Ahmet Fatih Ayyıldız ,

You could probably create an automation for this with a combination of manual trigger that 'requests input'.
Here's an example

Trigger

Cloning an Epic

Storing Epic key

Creating 'child item'

This actually only clones Epic and creates new child items (not cloning existing ones) > meaning you're actually creating those 'templates' within the automation rule. The same could apply to the Epic, so you wouldn't just clone that but use the create action.

In the end, when you would trigger this rule, the prompt could look like this:

So again, it's not actually cloning but selecting 'what to create', but I believe you get the point.

It could definitelly be improved a bit, but that's like the first thing that popped into my mind when seeing this.

Here's one official article about cloning: Automation: How to clone tasks/stories along with their sub-tasks

On top of that, there's an open feature request to improve the clone option in Jira: JRACLOUD-5052: Allow different "Clone Issue" options

Hope this helps.

Cheers,
Tobi

Peter_DevSamurai

Hi @Ahmet Fatih Ayyıldız ,

It lets you clone Epics/templates with hierarchy, then preview and edit issues before finalizing—selectively exclude subtasks by unchecking them in the preview dialog (no JQL needed).
Setup: Install from Marketplace > Clone from Epic view > Choose "Include subtasks" > Preview mode to pick/drop.

2. Easy Clone for Jira Cloud (Paid, free for instances with less than 10 users, but I think the pricing is lesser than the above one)

Deep clones Epics/subtasks while maintaining relationships. No direct selective UI, but pre-configure via templates or filters (less flexible than Clone Expert, but simpler if subtasks are grouped by labels).

But, you can try the below guide but it is not ideal for interactive. You can try automation but it's limited as 100 runs per month:

Pre-tag subtasks in your template with labels (ex: "Core", "Optional1", "Optional2").
Automation rule: Trigger "Issue cloned" (on Epic) -> Branch "For stories" -> Clone linked issues -> Condition: Label matches multi-select variable (prompt user for selection via form/email, but no direct UI. You can use Slack/Jira comment for input).

You can refer to the below link:

Automation Basics

Best,

Peter

Valerie Knapp_gp7rpj

Hi @Ahmet Fatih Ayyıldız , thanks for your post.

You could use Automation for something like this, for example, you could use an automation rule like this one, that when a certain type of Epic is created, so maybe a specific custom field is flagged, to create a series of tasks / sub-tasks - https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/112180

Deep Clone, as an app dedicated to this purpose, will have more functionality than the out-of-the-box automations, but I would encourage you to have a look at the automation template library, do some tests and see what you think.

When you have more details, please write again if you need more help or advice.

Cheers

Dorota Popowska - Vilisoft

Hi @Ahmet Fatih Ayyıldız

If you want to avoid writing JQL filters each time, I’d suggest looking at Clone Expert for Jira. It lets you clone a template Epic with its hierarchy and then decide in the preview which child items or subtasks should actually be included in the clone. It gives you a much more user-friendly way to control the scope of what gets cloned.

A useful part of this is that Clone Expert lets you flexibly decide how subtasks should be handled. You can exclude all subtasks entirely or select only the ones that should be cloned. The same applies to regular child tasks as well, so you can adjust the scope depending on the needs of a specific project.

You can also edit selected fields before creating the cloned work items, which helps reduce follow-up cleanup afterwards.

If you’d like, I can share more details on how this works. Here is the documentation as well: Link

Best,

Dorota

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud