Step 1 – Cloning option
For Epics:
If you’re cloning an Epic, locate the Clone template option in the Operations menu of the Epic issue. This action allows you to clone the Epic along with all its child issues and sub-tasks.
For any other Issue type:
If you’re cloning an issue that is not an Epic, select the Clone issue option in the Operations menu. This action enables you to clone the selected issue along with its sub-tasks.
The available cloning options will adapt dynamically based on the type of issue you’re working with, ensuring a seamless experience across all issue types.
Once you select the desired cloning action, the system will display a customizable cloning form, allowing you to adjust details such as the destination project, components, and other configurations before proceeding with the cloning process.
Step 2 – Destination Project
The first section, Destination Project, allows you to select the target project where cloned issues will be created.
Step 3 – Clone components
In the Clone Components section, choose specific components to include in the clone. These options apply to all issues selected for cloning.
Sub-tasks
When you select Sub-tasks, they will automatically appear in the main editing table, allowing for further customization and giving you the option to include them in the cloning process.
Attachments
If Attachments option is ticked, all attachments in Epic, linked issues and sub-tasks (if selected) are cloned.
Watchers
If Watchers option is ticked, watchers of Epic, linked issues and sub-tasks (if selected) are cloned.
Comments
If Comments option is ticked, comments from Epic, linked issues and sub-tasks (if selected) are cloned.
Issue Links
If Issue Links option is ticked, issue links within cloned issues are also cloned.
Step 4 – Cloning strategy
This step applies exclusively to the ‘Clone Template‘ action for Epics. If you are cloning a single issue, proceed to Step 6.
Select a Cloning Strategy to determine where linked issues will be cloned. Choose from the following options:
Linked issues cloned to the project where Linked issues already exis
Choose this strategy if linked issues should be created in the same project where template issues exist.
Use this strategy:
- If cloned epic and issues should be created in the same projects where template issues exist.
- If cloned Epic should be created in a different project and linked issues should be created in the same project where template issues exist.
Take a look at the picture below – you may see the result if one select this strategy.
Child issues cloned to the same project as Epic task
Choose this strategy if all linked issues should be created in the target project as was selected for New Epic.
Use this strategy:
- If you want to clone all issues (epic + linked issues) to one project even if templates issues are in various projects.
- If you want to clone linked issues to the same project where new epic will be created.
Take a look at the picture below – you may see the result if one select this strategy.
Step 5 – For cloud only – Cloning without an Epic
You can clone selected issues without linking them to an Epic. This provides added flexibility when you need to clone tasks independently.
This feature is currently available for Jira Cloud users. However, support for cloning without an Epic will soon be available for Jira Data Center and Server users as well.
Step 6 – Child issues and sub-task
Whether you’re cloning an Epic or any other type of issue, you can decide which child issues and sub-tasks should be included in the cloning process. This step ensures maximum flexibility in tailoring your cloned structure to your project needs.
Selecting Issues and Sub-tasks
-
All child issues and sub-tasks related to the selected issue will be displayed in a table.
-
Use the checkboxes on the left-hand side to select which child issues and sub-tasks should be included in the cloning process.
Remember that if sub-tasks are hidden via “Hide sub-tasks” button, selecting/unselecting all issues via top checkbox will not affect them.
If the Sub-tasks option is ticked, all sub-tasks associated with the selected issue, including those in child issues for Epics, will be displayed.

You can choose which sub-tasks associated with the selected issue you would like to clone. Additionally, you can modify the values of specified fields for further customization.

The possibility to hide/show all sub-tasks.

You can choose which sub-tasks in linked issues template you would like to clone.
You can change values of all fields – Additional fields.
Step 7 – Editing
Fields selection
Before cloning, you can change issues values. You can change or remove existing values for all fields visible on the linked issues list.
Please keep in mind that if you change values in the table, source template issues will be not changed.
You can select values visible in linked issues grid table. To add values to the list, please select proper custom fields in Additional fields editbox.
For both strategies: Child issues cloned to the project where Child issues already exist and Child issues cloned to the same project as Epic task, issue type can be changed.
Single edit
To change the value, just click on field you want to change and enter new value.
Bulk edit
If you want to provide the same value to all linked issues, you can use bulk edit option available for any fields.
To do it – just click on pencil icon next to the field name in the table header, enter the value/values, select edit option and click on the “Apply to all” button.
As a result, provided value/values are filled in all linked issues.
For cloud only – Find & Replace: Fast, Transparent Bulk Edits
Remember that if sub-tasks are hidden via “Hide sub-tasks” button, bulk edit will not affect them.
Assigning Sprints to Issues
During the cloning process, you can assign specific sprints to child issues directly from the template. This feature is particularly useful when replicating tasks for upcoming sprints or project phases.
*This feature is currently available only for Cloud users.
Step 8 – Cloning
Once the selected issue and its associated sub-tasks or child issues are ready for cloning, simply click the ‘Clone‘ button. The system will create a new issue or Epic along with the selected items, preserving the desired structure and details.