...
...
...
This page explains how a Jira administrator can use the Clone Plus Configuration User Interface (UI) to help manage clone operation customizations. To view the Clone operations configuration page and configure various settings of the app you can navigate to either:
Jira settings > Manage apps > locate the app and expand the panel > click Configure, or
Jira settings Settings ⚙️ > Apps > BOBSWIFT - CLONE PLUS FOR JIRA - Clone operations, or
Apps menu > Apps menu >Clone Plus for Jira > click Configuration page in the welcome screen
Configuration
...
Enable localization
If enabled, this option allows users to view the UI as per their specified language settings through their Atlassian account. Currently, the app supports the following languages:
German
French
Spanish
Italian
...
If this parameter is not enabled, users can still translate the texts and labels using the Translate link available on individual screens of the app.
...
in the Get started page.
Clone operations
...
This page lists all the customized clone operations and allows you to create new clone operations to use them while cloning issues in various projects. Clone operations allow you to control the behavior of cloning issues. They comprise a set of:
conditions that specify whether or not a clone operation is valid for the specific projects, issue types, etc.and so on, and
properties that limit copying or excluding specific fields while cloning.
You have a default Clone Plus operation configured Plus operation configured with the app. Use the toggle button in the Active column to make the respective clone operation active or inactive. Inactive clone operations are not displayed while cloning an issue.
| Note |
|---|
When the user is cloning an issue and is already on the Create issue page, if you make the clone operation inactive that the user is using to clone, the issue will be cloned as this page is from Jira. |
You can:
see the total count of clone operations on the top left
view a maximum of 10 clone operations per page
click the respective page number, or
or or
to navigate to next or previous page respectively
Create clone operation
To create a new clone operation:
...
Click +Create clone operation to navigate to Step 1 for configuring various fields.
Perform the following:
...
Conditions - Set the following to make the clone operation available only for the specified values:
Projects
Issue types
Status
You can select multiple values.
Allow Bulk Clone - Turn this toggle On to enable the clone operation for bulk cloning. Users can clone multiple issues from multiple projects with bulk cloning. By default, this toggle is enabled.
| Note |
|---|
|
...
Click Next to navigate to Step 2.
Provide values for the following fields options to control the clone operation behavior with the specified values:
Set fields - Select one or more field(s) for which you want to define values to be used while cloning an issue. To define a value, you can either select from the available list or use substitution variables.
| Note |
|---|
|
Clone properties: Select one or more fields to control the clone operations as defined in this section.
...
Property
...
Description
...
Field excludes
...
This behavior ensures the field values are cleared in the cloned issue.
...
This behavior allows the fields to be directly copied over to the newly cloned issue.
| Note |
|---|
Ignore fields behavior:
|
...
This behavior allows the cloned issue to be cloned into the specified projects. Select one of the following options from the available list:
- One or more projects from the list of every project available in your Jira instance.
- All projects - displays all the projects while cloning.
- Same project - enables cloning an issue into the same project, by default.
- Original project - enables cloning an issue into the original project, by default.
...
This behavior allows you to specify the issue types that are available when cloning. Select one of the following options from the available list:
- One or more issue types from the list of every issue type available in your Jira instance.
- All issue types - displays all the issue types while cloning.
- Same issue type - enables cloning an issue into the same project, by default.
- Original issue types - enables cloning an issue into the original project, by default.
...
Clone options
Select one or more options from the list to copy the respective issue detail to the cloned issue. You can also activate or de-activate the options in the Active column by switching the toggle button On or Off respectively. If a clone option is set to active, the user can select or de-select the option as needed while cloning an issue. If set to inactive, the clone option is disabled for any further modification during cloning.
By default, all options are un-selected and are in active mode.
The available options are:
Copy attachments
Copy watchers
Copy worklogs
Copy comments
Copy subtasks
Copy subtask estimates to cloned subtasks
Copy parent issue's reporter to each cloned subtask
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
You can also Select all options to copy all the issue details to the cloned issue.
| Note | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Click Next to navigate to Step 3 or Back to go back to step 1.
...
Specify the Clone operation name and Description.
...
Click Save to save the operation. The newly created operation is displayed in the Clone operations screen. You can also click Back to go back to the previous step(s) and modify the clone operation details.
Edit clone operation
To edit a clone operation:
Select ellipsis > Edit operation of the respective clone operation, to navigate to step 1 of edit page.
Follow steps 2 to 7 from the previous section to save the changes.
Delete clone operation
Refer to the image from the previous section.
To delete a clone operation:
...
Select ellipsis > Delete operation of the respective clone operation.
...
References