| Div | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
On this page
|
Summary
One of the major benefits of the Clone Plus for Jira is the ability to customize clone operations to suit your development process. This capability has been provided since the initial version of the plugin. Since version 3.x, we have made it possible to provide very sophisticated customization capabilities without programming. It still requires a clear understanding of your JIRA system and processes, but, the implementation can be done via a property-based configuration with average Jira administration knowledge and some careful testing. Open an issue if you need more extensive customization than what is currently provided.
...
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 (since 6.5)
copy subtasks of issues in epic (since 6.5)
copy subtasks estimates to cloned subtasks of issues in epic (since 6.5)
copy parent reporter (since 6.6)
...
option.copyLinks = true
1.option.copyAttachments = false
2.option.copyWorklogs = hide
1.plus.option.copyWatchers = false
...
How to clone an epic with all the child issues from the same project - 6.5
How to clone an epic with all the child issues from different projects - 6.5
...
Substitution variables
...
Current issue fields are available as substitution variables for the setting of fields
...
1.set.summary = BLOCKER: %original_summary%
...
...
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
...
...
Include field list to be displayed while cloning
...
In some scenarios, certain fields must be displayed in the Clone UI
...
1.fieldIncludes = priority, custom2
...
...
Ignore field list for fields that should not be shown on clone screen
...
Control fields that are allowed to be changed by the user during the clone operation
...
1.ignoreFields = Special
...
...
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
...
...
Setting standard and custom fields
...
1.set.description = Some standard description
...
...
Feature | Overview | Examples | References | |||
|---|---|---|---|---|---|---|
1 | Up to 16 unique clone custom clone operations can be defined |
|
| |||
2 | Conditioning |
|
| |||
3 | Clone option defaults |
|
| |||
4 | Substitution variables | Current issue fields are available as substitution variables for the setting of fields | 1.set.summary = BLOCKER: %original_summary% | |||
5 | 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 | |||
6 | Include field list to be displayed while cloning | In some scenarios, certain fields must be displayed in the Clone UI | 1.fieldIncludes = priority, custom2 | |||
7 | Ignore field list for fields that should not be shown on clone screen | Control fields that are allowed to be changed by the user during the clone operation | 1.ignoreFields = Special | |||
8 | Mapping fields from original issue to a new value in the target issue conditioned on original issue field values |
|
| |||
9 | Setting standard and custom fields | 1.set.description = Some standard description | ||||
10 | Bulk Clone (since 6.8) | Clone multiple issues at once to the same project or different project
|
...
| autoNumber | true |
|---|
...
Feature
...
Overview
...
Examples
...
References
...
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 actions
...
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
Condition-based on role
1.condition.ZCLONE.*.* = true
2.condition.*.*.1 = true
1-plus.role.ZCLONE = Developers
...
Bulk Clone (since 6.8) | Clone multiple issues at once to the same project or different project
|
Getting started
Getting started with customization is the best place to start.
...