---
title: "Single clone - Cloud"
canonical: "https://support.appfire.com/space/JCPP/71270971/Single%20clone%20-%20Cloud"
format: markdown
---
> Macro (aura-html)

> ℹ️ This is the documentation for Clone Plus for Jira Cloud. If you are using Clone Plus for Jira Data Center, refer to the [Single clone - Data Center](https://appfire.atlassian.net/l/cp/Y1wRa0zy) page.

This page provides details for cloning an issue, including all required field settings. A single clone helps you to duplicate an issue within a project by copying the information, such as attachments, comments, subtasks, links, worklogs, watchers, and so on, all at once thus saving time.

> ℹ️ When you try to perform a Clone Plus* *operation on a project for which a clone operation is not configured, you are prompted with an error message conveying that you cannot proceed further as Clone Plus for Jira is not configured for the project.

You can also refer to the following various clone features using single clone:

> Macro (contentbylabel)

# Steps

1. Select an issue you want to clone in your Jira instance.
2. In the top-right corner, select **the three dots** > **Clone Plus*** *option or select the **Clone Plus icon** quick-add button in any issue.
3. On the *Clone Plus for Jira *page, do the following:
  1. In the **Clone operation** drop-down list, select the required clone operation.
  2. In the **Project** drop-down list, select the required project.
  3. In the **Issue type** drop-down list, select the required issue type.
  4. In the **Clone options** section, select the required clone option.
4. Click **Clone**.
5. On the *Create issue *page, select values for all the issue fields as required.
6. Click **Create **to clone the issue.   
The issue is cloned as configured. You can see a success message with the following details:
7. Click **View clone(s)** to view the cloned issue(s).

The following video shows you how to clone an issue.

> Macro (iframe)

    

> ℹ️ - On the *Clone Plus for Jira *page, the values available for selection for **Clone operation**, **Project**, **Issue type**,* *and **Clone options** fields depend on the respective [clone operation configured ](https://appfire.atlassian.net/l/cp/Z6bpVQR4)by the Jira administrator.
> ℹ️ - When you are cloning an issue and you are already on the **Create issue** page, if your Jira administrator makes the clone operation inactive that you are using to clone, the issue will be cloned. For more details, refer the [Clone Plus for Jira Configuration](https://appfire.atlassian.net/l/cp/BNP4dsS8) page.
> ℹ️ - In the **Clone options*** *section,* *the* ***Issues in epic*** *and the associated options are enabled only when the **Issue type*** *selected is *Epic*.
> ℹ️ - While cloning an issue, when you select:
> ℹ️   - **Comments**, the original commentator is replaced with the user cloning the issue.
> ℹ️   - **Links**, a Confluence link from the issue being cloned is copied as a web link to the cloned issue.
> ℹ️   - **Attachments**, the images or any form of media added to rich text editor fields such as description, comments, or environment, are copied to the cloned issue. If this clone option is not selected, a broken image is displayed in the respective field of the cloned issue.
> ℹ️ - On the *Create issue *page:
> ℹ️   - **Project*** *and **Issue type*** *values are copied from the *Clone Plus for Jira *page.
> ℹ️   - The issue fields configuration is similar to native Jira issue configuration screen. However, some of the fields and respective values displayed are based on the respective [clone operation configured](https://appfire.atlassian.net/l/cp/Z6bpVQR4) by the Jira administrator.
> ℹ️   - You can make further changes to the issue fields and switch between **Configure fields > All | Custom**. This option provides the flexibility to configure all the fields or customize the fields based on your project requirements.
> ℹ️   - You can optionally select the **Create another** checkbox* *to create another issue with the same issue details.