Page tree

Versions Compared

Key

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

Step I - cloning option

In the menu of any Epic issues you can find new option Clone template.

Tip

New option Clone template is available only in Epic issues.

If you click on Clone template option window where issues details can be edited before cloning will be displayed.

Example:

Step II - new Epic details

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



Field nameDescription

New Project

Here target project for new Epic can be selected. Current project can be kept or different project can be selected. User can see only this projects where have access to.

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.

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

New Epic Summary

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

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

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 left empty.

New Epic Due Date

New Due Date for new Epic can be chosen.

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

Description

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

Step III - 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 be cloned.

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

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

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

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

Step IV - cloning strategy

In the section Epic linked issues clone strategy can be chosen.


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

Chose this strategy if project structure for linked issues should be kept as is in template epic.

Example:

  1. If in your template epic are linked issues from different projects and new issues should be created in the same projects as 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.
Linked issues cloned to the same project as Epic task

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

Example:

  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.

Step V - linked issues

Selection

Editing

Bulk editing

dsds