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

Cloning Structure , tasks and subtasks on the same JIRA project

RomainCUVELLIER

Hello all,

I have a question about the "structure" module

I am unable to clone the structure along with all the associated tasks and the general request.

When I save the structure, it actually creates a new structure and places the same tasks in this new structure.Thats its problematics.

What I need is to recreate exactly the same tasks (like a clone of the tasks) so that I can use separate structures for each new services with my differents client, based on a "template" structure that we will clone with the associated tasks.

For more to be clear, I am trying to clone my template structure within the same JIRA project. The idea is that we have created a template of a structure with a set of tasks for each type of project of my society and services. Each project (JIRA project) represents a type of service. However, I will need to duplicate the tasks and the structure multiple times based on the number of times we will perform these services.

I know that we can clone tasks by opening them one by one and using the clone option, but given the number of tasks we have in our template, it's very complicated to do that. Additionally, when selecting all the tasks and using “bulk edit”, I don't see the cloning option appearing.

Thank you for your help on this matter. Have a great day!

Accepted answers

Stepan Kholodov

Hello @RomainCUVELLIER

If you're asking about:
- the ability to clone issues when copying a structure
- in our app Structure Cloud,

then, such functionality is currently not implemented. Structure uses Jira's own bulk edit functionality, and it doesn't include the cloning option by default. But we do have a feature request in our backlog to make it possible in the future.

I hope this helps. If you have more questions about Structure, please reach out to us directly at our support portal.

Best regards,
Stepan
Tempo (the Structure app vendor)

All comments

Stepan Kholodov

RomainCUVELLIER

Hello to you, thank you for your response.

In this case, is it possible to create ticket clones while keeping the architecture I have in my "template" structure and adding them to a new structure?

Stepan Kholodov

It depends on your setup - how the structure is built, and what the clones look like. For example, if clones are different from the original issues, and they can be returned by a JQL query, you can create a new structure with an inserter with this query. Every time when you create a clone that matches the query, it will be automatically added to the new structure. Additionally, you can configure other generators for creating the hierarchy based on the data of the clones, if needed.

Best regards,
Stepan

RomainCUVELLIER

Ho ok, beacause I saw that it was possible before, but with the new menu of Jira Service Management, I don't see how to do ithttps://tempo-io.atlassian.net/servicedesk/customer/portal/6/article/3677686149

Luka Hummel - codefortynine

Hi @RomainCUVELLIER and welcome to the community!

From what you describe, you need to clone Jira issues from your template (tasks + subtasks), ideally within the same project and in bulk. That’s exactly what our app Deep Clone for Jira is built for.

Two quick ways to spin up a fresh copy of your template work

Clone a whole hierarchy (Epic → tasks → subtasks)
If your template lives under one (or several) epics, use Epic/Tree Clone:
1. Open the template epic and click Actions (•••) > Deep Clone > Epic/Tree Clone.
2. Choose Epic/Tree Clone.
3. Set Target project to the same project (or another one, if needed).
4. Under Advanced options, keep the defaults or fine-tune what should be copied (e.g., Comments, Attachments).
5. Optionally add a Prefix summary (e.g., “[Client ACME]”) to label the fresh set.
This creates a new, independent copy of the entire tree you can work with separately.
Clone many template issues at once
If your template is a set of issues spread across epics or different types, use Bulk Clone:
1. Go to Apps > Deep Clone > Bulk Clone.
2. Select your template issues via JQL, a saved filter, or by project.
3. Set Target project to the same project (or another one, if needed).
4. Configure the clone as described above.

For recurring client work, save your setup as a Preset so you can re-run the same clone configuration in seconds.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

structure

jira-service-management-cloud

jira-service-management