...
Tip |
---|
Start with Getting started with customization before diving into the details here. |
Mapping
...
keys
Mappings keys are dot-separated property names: prefix.class.qualifier1.qualifier2.qualifier3.qualifier4.
...
Expand |
---|
|
Class | project | Qualifier 1 | project (The key or id )of the project. | Qualifier 2 | The id of the issue type (id). | Qualifier 3 | status (id)The id of the status. | Value | target project (The key or id )of the target project. | Example without prefix | project.JRA.1.* = JRA2
project.*.*.* = JRA
| Example description | Clone to JRA2 any bug (1) from JRA project. Set target project as JRA and create issues in the JRA project. |
|
Expand |
---|
title | Set target component |
---|
|
Class | project-component | Qualifier 1 | project (The key or id )of the project. | Qualifier 2 | component (The name or id )of the component. | Qualifier 3 | NA | Value | target project (The key or id )of the target project. | Example without prefix | project-component.JRA.C1 = JRA2
| Example description | Clone to JRA2 any JRA issue with component C1. |
|
Expand |
---|
|
Class | type | Qualifier 1 | project (The key or id )of the project. | Qualifier 2 | The id of the issue type (id). | Qualifier 3 | status (id)The id of the status. | Value | The id of the target issue type (id). | Example without prefix | type.JRA.* = 1
| Example description | Clone JRA issues to a bug (1). |
|
Expand |
---|
title | Set target component |
---|
|
Class | component | Qualifier 1 | component (name)The name of the component. | Qualifier 2 | NA | Qualifier 3 | NA | Valuecomponent | (name)The name of the component. | Example without prefix | component.C1 =
| Example description | Remove component C1 from cloned issues. |
|
Expand |
---|
|
Class | version | Qualifier 1 | version (name)The name of the version. | Qualifier 2 | NA | Qualifier 3 | NA | Valueversion | (name)The name of the version. | Example without prefix | version.V2 = V1
| Example description | Map version V2 to V1 |
|
Expand |
---|
|
Class | linkType | Qualifier 1 | NA | Qualifier 2 | NA | Qualifier 3 | NA | Value | Link The name of the link. | Example without prefix | linkType = Blocks
linkType =
| Example description | Uses the Blocks link instead of the default clone link. No link will be added. | Note | Must be the name of the link as shown on the Issue Linking admin panel. See How to customize automatic clone linking. |
|
Expand |
---|
|
Class | linkDirection | Qualifier 1 | NA | Qualifier 2 | NA | Qualifier 3 | NA | Value | Link The direction of the link. | Example without prefix | linkDirection = INWARD
| Example description | Uses an INWARD link instead of the default OUTWARD link. |
|
Expand |
---|
title | Set clone option default behavior |
---|
|
Class | option | Qualifier 1 | The name of the option name. | Qualifier 2 | NA | Qualifier 3 | NA | Value | true or false The value of the option, that is, true, false, or hide | Example without prefix | option.copyAttachments = true
option.copyComments = hide
| Example description | Set the Clone attachments option to default to checked (true) or not checked (false). Use hide to prevent the option from being shown to users. No action will be taken. | Note | Valid option names are: Examples: Note |
---|
While using the copyEpicIssues option with Clone ++ operation, if the issue type of the source epic does not exist in the target project, the default issue type is assigned to the cloned issue. If there is no default issue type defined, the issue type specified first in the order is assigned to the cloned issue. When all the clone options are hidden during configuration, the Clone Options label is not displayed in the Clone window while cloning an issue. If the Copy subtasks clone option is used while cloning an issue and the respective subtask workflow is configured with a validator on any of the fields or a condition fails, the subtasks are not created.
|
|
|
Expand |
---|
title | Set clone option additional behavior |
---|
|
Anchor |
---|
| Set-clone-option-additional-behavior |
---|
| Set-clone-option-additional-behavior |
---|
|
Class | option | Qualifier 1 | option The name of the system or custom nameoption. | Qualifier 2 | NA | Qualifier 3 | NA | Value | The value of the system or custom option, that is, true or false. | Example without prefix | option.copycustomfield_11060 = true
| Example description | Set the custom option field to default to checked (true) or not checked (false). |
|
Expand |
---|
title | Restrict who can see clone operation |
---|
|
Anchor |
---|
| cloneProps_RestrictCloneAction |
---|
| cloneProps_RestrictCloneAction |
---|
|
Class | role | Qualifier 1 | project (The key or id )of the project. | Qualifier 2 | NA | Qualifier 3 | NA | Valuerole | (name)The name of the role. | Example without prefix | role.JRA = Administrators, Developers
| Example description | Restrict clone operation for project JRA to Administrators or Developers roles. | Note | Multiple roles can be specified using a comma separated list. |
|
Expand |
---|
|
Class | condition | Qualifier 1 | project (The key or id )of the project. | Qualifier 2 | The id of the issue type (id). | Qualifier 3 | status (id)The id of the status. | Qualifier 4 | project category (The name or id )of the project category. | Value | The value of the condition, that is, true or false | Example without prefix | condition.*.*.*.* = true
condition.JRA.*.*.* = false
| Example description | Show action for all projects except JRA. |
|
...
Expand |
---|
|
This behaviour excludes the fields from being copied from the parent issue to the target issue and the fields are not displayed on the UI when cloning an issue. A comma-separated list of System field names or custom field names or IDs (like customfield_10100) that are hidden in the cloned issue. Examples Setting | Description | fieldExcludes = fixVersions
| Do not copy the fixVersion field for app provided Clone+ and Clone++ operations | 1.fieldExcludes = ${fieldExcludes}, custom2
| For the specific custom operation 1: |
|
Expand |
---|
|
This behaviour displays the fields on the UI and includes the fields from being copied from the UI when cloning an issue. A comma-separated list of custom field names or IDs that are to be copied. Note |
---|
If a field specified in both fieldIncludes and fieldExcludes, it is not displayed in the UI when cloning an issue. |
Examples Setting | Description | fieldincludes = Priority
| Show the Priority field for app provided Clone+ and Clone++ operations. | 1.fieldIncludes = ${fieldIncludes}, Priority
| For custom operation 1, show the Priority field in the UI. |
|
Expand |
---|
|
This behaviour excludes the fields from being displayed on the UI and the fields are being copied from the parent issue to the target issue when cloning an issue. A comma-separated list of System field names or custom field names or ids that will not show up on the UI. If you want to set custom fields via properties and they are on the create screen, then they need to be on the ignoreFields list. Examples Setting | Description | ignoreFields = custom2
| Do not show in the UI but copy custom2 field for app provided Clone+ and Clone++ operations. | 1.ignoreFields = priority, custom2
| Do not show the priority or custom2 fields on the Clone screen for custom operation 1. |
Note |
---|
Not applicable to the Attachment field as the copy attachments option is available while cloning an issue with attachments. |
|
...
Expand |
---|
|
This behaviour enables the issue types to be included for operations that allow the issue types to be changed. A comma-separated list of issue types. Examples Setting | Description | issueTypeIncludes = Bug, "New Feature"
| For the app provided Clone++ operation, include only these issue types in the Type list (provided these issue types are available in the cloned project). | 1.plus.issueTypeIncludes = Bug, "New Feature"
| For the custom 1 plus operation, include only these issue types in the issue type list (provided these issue types are available in the cloned project). |
|
...