1

Up to 16 unique clone custom clone operations can be defined

• Name can be customized to reflect the purpose related to your process

• Each can be enabled independently as required

• Choose either

  • clone to the same project and issue type

  • clone to a different project or different issue type

• 1.label = Escalate to Engineering

• 1.tooltip = Creates a task for Engineering

• 2.label = Create a Requirement

How to enable and disable actionsclone operations 

Clone properties 

2

Conditioning

• Each can have unique conditions that determine when the action is available

• Generic on condition fields

• Condition-based on fields

  • project

  • issue type

  • status

  • project category

• Condition-based on role

• Conditioning is applied for bulk clone

• 1.condition.ZCLONE.*.*.* = true

• 2.condition.*.*.1.* = true

• 1-plus.role.ZCLONE = Developers

• 1.condition.*.*.*.newcategory = true

Clone properties 

3

Clone option defaults

• Set default options

• Options available

  • copy attachments

  • copy watchers

  • copy comments

  • copy subtasks

  • copy estimates

  • copy parent versions

  • copy links

  • copy issues in epic

  • copy subtasks of issues in epic

  • copy subtasks estimates to cloned subtasks of issues in epic

  • copy parent reporter

• option.copyLinks = true

• 1.option.copyAttachments = false

• 2.option.copyWorklogs = hide

• 1.plus.option.copyWatchers = false

• Clone properties

• How to clone an epic with all the child issues from the same project

• How to clone an epic with all the child issues from different projects

4

• Set additional options

• You can add both custom fields and system fields, such as:

  • copy custom field

  • copy assignee

  • copy summary

  • copy due date

  • copy fix Version/s

  • copy labels

  • copy security

  • copy component/s

• 1.option.copycustomfield_11060 = true

• 1.option.copypriority = false

• 1.option.copyfixVersions = true

• Clone properties 

• How to enable cloning for any custom or system fields in the user interface

5

Substitution variables

Current issue fields are available as substitution variables for the setting of fields

1.set.summary = BLOCKER: %original_summary%

• Substitution variables

• Setting fields

• Clone properties 

6

Exclude field list to prevent copying to clone

In many use cases, certain fields should not be copied to the target issue

1.fieldExcludes = custom2, custom three

Clone properties 

7

Include field list to be displayed while cloning

In some scenarios, certain fields must be displayed in on the Clone UI

1.fieldIncludes = priority, custom2

Clone properties 

8

Ignore field list for fields that should not be shown on clone screenControl fields that are allowed to be changed by the user during the clone operation

In some scenarios, certain fields must not be displayed on the Clone UI

1.ignoreFields = Special

Clone properties 

9

Mapping fields from original issue to a new value in the target issue conditioned on original issue field values

• Map to a new project based on the project, issue type, and status

• Map to a new project based on project and component

• Map to a new type based on the project, issue type, and status

• Map to a new component based on the component name

• Map to a new version based on the version name

• 1.project.SUPPORT.*.* = ENG

• 1.component.UI = User interface

Clone properties 

10

Setting standard and custom fields

1.set.description = Some standard description

• Setting fields

• Clone properties 

11

Bulk Clone

Clone multiple issues at once to the same project or different project