Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Step 1 - cloning option

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

Tip

New option Clone template option is available only in Epic issues only.


If you click on Clone template option, system will dispaly dispalys form where issues details can be edited before cloning . Form will look like on picture below. 


Step 2 - new Epic details

In first section some Epic details can be edited before being cloned.



Field nameDescription

New Project

Here By default the target project for new Epic can be selected. Current project (defined in the template) can be kept or different project can be selected from the list of projects accessible for the is the same as in cloned Epic. Target project could be change for any project accessible for logged user.

New Epic Name

I that field a new Epic Name can be entered. Epic Name can be changed completely or can be kept as is in template.This

The field can't be empty - this is mandatory to clone issue.

New Epic Summary

I that field a new Summary can be entered. Summary can be changed completely or can be kept as is.

This The field can't be empty - this is mandatory to clone issue.

New Epic Assignee

I that field a new Assignee can be selected. Assignee can be changed completely or can be kept as is.If your workflow doesn't require this field, it can be empty..

Up to JIRA set up, the field can be mandatory or optional. 

New Epic Due Date

New Due Date for new Epic can be chosen.

If your workflow doesn't require this field, it can be empty.

Description

Epic's description Description can be changedentered. To edit this field, click on option.

Step 3 - clone components

Next section is Clone components. Here can be selected what elements will be cloned. This is related to Epic and linked issues selected to User may make decision which issues' components must be cloned. 

If Sub-tasks option is ticked, it means that all sub-tasks in Epic and in linked issues will be are cloned.

If Attachments option is ticked, it means that attachments attached to all attachments in Epic, linked issues and sub-tasks (if selected) will be are cloned.

If Watchers option is ticked, it means that watchers from of Epic, linked issues and sub-tasks (if selected) will be are cloned.

If Comments option is ticked, it means that all Comments in Epic linked , comments from Epic, linked issues and sub-tasks (if selected) will be are cloned.

Step 4 - cloning strategy

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


Epic cloner strategies

StrategyDescription
Linked issues cloned to the project where Linked issues already exist

Choose this strategy if linked issues should be created in the same project where template issues exist.

Use this stategy:

  1. If in your template epic are linked issues from various projects and new cloned epic and issues should be created in the same projects as where template issues exist.
  2. If cloned Epic should be created in 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 uses select this strategy.

Choose this strategy if linked issues should be created in the same project where template issues exist.

Linked issues cloned to the same project as Epic task

Chose this strategy if all linked issues should be created in the target project as was selected for New Epic.

Use this stategy:

  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 uses select this strategy.

Chose this strategy if all linked issues should be created in the target project as was selected for New Epic.


Step 5 - linked issues

You can decide if you want to clone all linked issue or only a few. On the right side of the list of linked issues there are checkboxes available. Tick -hand side, tick all you want to clone.

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.

Warning

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.


Tip

For strategy Linked issues cloned to the project where Linked issues already existstrategy, issue type can't be modified.

For strategy Linked issues cloned to the same project as Epic task stategy, issue type can be changed.

Single edit

To change the value, just click on field you want to change and provide enter new value. 


Bulk edit (replacement)

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  pen-icone, then enter the value/values and click on the "Apply to all" button.


As a result, provided value/values are filled in all linked issues. 

Step 7- Cloning

If epic and linked issues are ready for the cloningbeing cloned, just click on the   button and new Epic with selected issues will be creted.