---
title: "Clone Plus for Jira configuration - Cloud"
canonical: "https://support.appfire.com/space/JCPP/211255303/Clone%20Plus%20for%20Jira%20configuration%20-%20Cloud"
format: markdown
---
> Macro (aura-html)

# Create clone operation

The following video shows you how to create a clone operation.

> Macro (iframe)

To create a new clone operation: 

**Step 1**

- On the Clone operations page, click **+ Create clone operation**.  
The *Conditions* page is displayed.

**Step 2**

On the *Conditions* page, do the following:

1. In the **Projects** drop-down list, select one or more projects for which you want to set conditions.
2. In the** Issue types **drop-down list, select one or more issue types for which you want to set conditions.
3. In the** Status **drop-down list, select one or more statuses for which you want to set conditions.
4. Turn on the **Allow Bulk Clone** toggle to enable the clone operation for bulk cloning. You can clone multiple issues from multiple projects with bulk cloning. By default, this toggle is turned on.
5. Click **Next**.  
The *Properties* page is displayed.

> ℹ️ - Select the **Display for all projects**, **Display for all issue types**, or **Display for all status** checkbox, if you want to set conditions for all the projects, issue types, or statuses respectively. By default, this checkbox is selected.
> ℹ️ - The **Allow Bulk Clone** toggle is:
> ℹ️   - Turned off for all the clone operations created prior to the introduction of the Bulk Clone feature to Clone Plus. Administrators must manually turn on this toggle, if required.
> ℹ️   - Turned on* *for all those clone operations [migrated](https://appfire.atlassian.net/wiki/x/e4g-B) from a server instance to cloud.* *
> ℹ️ - Once this toggle is turned on, the clone operation is available for all projects, issue types, and statuses.

**Step 3**

On the *Properties* page, do the following:

1. In the **Set fields** section, do the following:
  - In the **Select a field** drop-down list, select a field for which you want to define values to be used while cloning.
  - In the **Select** drop-down list, define a value for the field either by selecting a value from the available list or using [substitution variables](https://appfire.atlassian.net/l/cp/syUXh0N5).
  - Click **+ Add set field** to add more fields and assign value to them.
2. In the **Select field includes **drop-down list, select one or more fields you want to copy to the cloned issue.  The field values are copied to the cloned issue irrespective of the changes while cloning.
3. In the **Select field excludes** drop-down list, select one or more fields you want to be excluded in the cloned issue. The field values are excluded for the cloned issue even when you add or edit them while cloning.
4. In the **Select Project includes** drop-down list, select one of the following:
  - One or more projects you want to include while cloning.
  - **All projects** to include all the projects while cloning.
  - **Same project** to clone an issue into the same project by default.
5. In the **Select Issue type includes** drop-down list, select one the the following:
  - One or more issue types you want to be available while cloning.
  - **All issue types** to display all the issue types while cloning.
  - **Same issue type** to clone an issue into the same project by default.
6. Select the **Add link** checkbox to create an issue link from the original issue to the cloned issue.
7. In the link drop-down list, select the required link from the original issue to the cloned issue while cloning. By default, the **is cloned by** option is selected. You can select any link available on the *Settings* ⚙️  >* Issues* > *Issue linking* page.
8. In the **Clone Options** section, do the following:
  - Select the **Select all** checkbox to copy all the issue details to the cloned issue. (or)
  - Select one or more options from the list to copy the required issue details to the cloned issue. The available options are:
    - **Issues in epic**
      - **Subtasks of issues in epic**
      - **Subtasks estimates of issues in epic to cloned subtasks**
    - **Subtasks**
      - **Subtasks estimates to cloned subtasks**
      - **Reporter of parent issue to each cloned subtask**
      - **Fix and affect versions from parent issue to each cloned subtask**
    - **Attachments**
    - **Links**
    - **Versions**
      - **Create versions if they aren’t available in the target project**
    - **Components**
      - **Create components if they aren’t available in the target project**
    - **Comments**
      - **Keep original comment date**
    - **Worklogs**
    - **Watchers**
    - **Jira issue properties apps (Smart Checklist and more)**
    - **Checklists for Jira**
  - In the **Active*** *column, you can turn on or off the toggle to activate or de-activate the available clone options. If a clone option is set to active, you can select or clear the option as required while cloning. If a clone option is set to inactive, the clone option is disabled for any further modification while cloning.
9. Click **Next**.  
The *Save clone operation* page is displayed.

> ℹ️ - For** Set fields** section:
> ℹ️   - Fields defined are not applicable to sub-task(s) cloning.
> ℹ️   - When you bulk clone, the defined values (apart from given substitution variables) provided in this field for versions* *(**Fix versions**, **Affects versions**) are not set in the cloned issues.
> ℹ️ - The* ***Ignore fields*** *section:
> ℹ️   - Is not applicable to sub-task(s) cloning.
> ℹ️   - Is a default behavior in bulk cloning, that is, all the field values of issues being cloned are copied to the cloned issues irrespective of the fields mentioned in this section.
> ℹ️ - Select the **Select All **checkbox to include all the projects or issue types while cloning. By default, this checkbox is selected.
> ℹ️ - The **Issues in epic**, **Subtasks of issues in epic**, and **Subtasks estimates of issues in epic to cloned subtasks **clone options are not applicable while bulk cloning.
> ℹ️ - When you select the **Comments*** *clone option while cloning an issue, the original commentator is replaced with the user cloning the issue.

**Step 4**

On the *Save clone operation *page, do the following:

1. In the **Clone operation name** field, enter the name you want.
2. In the **Description** field, enter the description for the clone operation.
3. Click **Save**.  
A new clone operation is created and displayed on the *Clone operations *page.

> ℹ️ On each page, you can click **Back **to go back to the previous pages and modify the clone operation details.

# Edit clone operation

To edit a clone operation:

1. Select **ellipsis ***>**** *****Edit operation** of the clone operation that you want to edit.  
The *Edit clone operation* page is displayed.
2. On the *Edit clone operation* page, edit the required changes .
3. Click **Save**.  
The edited clone operation is displayed on the *Clone operations *page.

# Delete clone operation

To delete a clone operation:

1. Select **ellipsis > Delete operation **of the clone operation which you want to delete.  
The* Delete clone operation *dialog box is displayed.
2. On the *Delete clone operation* dialog box, click **Delete operation**.The clone operation is deleted.