Cloning actions

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.

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.

Cloning set up

The first section, Destination Project, allows you to select the target project where cloned issues will be created.

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.

Cloning strategy

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:

1. If cloned epic and issues should be created in the same projects where template issues exist.
2. 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:

1. If you want to clone all issues (epic + linked issues) to one project even if templates issues are in various projects.
2. 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.

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.

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.

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.

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.

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.

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

For cloud only – Adding

You can add new issues directly within the cloning process, ensuring a fully customized issue hierarchy before cloning is finalized. This feature allows you to enhance your template structure without manually creating new issues after the cloning process.

During the cloning process, you’ll see a + Add Issue button above the issues edit table. Clicking this button allows you to add a new issue to the structure.

• Newly added issues will appear as additional rows in the edit table, where you can define all key details before cloning.

• These issues won’t have an issue key yet – they will be created only after the final cloning action is confirmed.

• Default field values are applied, as if creating a new issue from scratch.

• Once a new issue is added to the table, you can customize it just like any other issue within the hierarchy.

All configured new issues will be created as part of the cloned hierarchy, maintaining the structure and all customizations applied during the cloning process.

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.