Cloning process

Step 1 – Cloning option

In the Operations menu in any Epics you can find the option Clone template.

Clone template option is available in Epic issues only.

If you click on Clone template option, system dispalys form where issues details can be edited before cloning like in the picture below.

Step 2 – Destination Project

In the first section Destination Project can be edited before being cloned.

Step 3 – Clone components

Next section is Clone components. User can make a decision which issues’ components must be cloned. This applies to all issues that will be cloned.

Sub-tasks

Sub-tasks will be described in section 5 – Child issues and sub-task.

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

In section Epic linked issues, clone strategy can be chosen. There are two strategies available:

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 -Child issues and sub-task

You can decide if you want to clone all linked issue or only some specific. On the left-hand side, tick all you want to clone.



Remember that if sub-tasks are hidden via “Hide sub-tasks” button, selecting/unselecting all issues via top checkbox will not affect them.

If Sub-tasks option is ticked, all sub-tasks in Epic and in child issues will be shown.

You can choose which sub-tasks in Epic template you would like to clone. You can change values of specified fields.

The possibility to hide/show all sub-tasks.

Remember that all selected sub-tasks will be cloned no matter if they are hidden or not!

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 6 – 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.