Single Clone

This is the documentation for Clone Plus for Jira Server/Data Center. If you using Clone Plus for Jira Cloud, refer the Single Clone - Cloud page.

This page provides the details of clone operations for cloning an issue with all the required issue field settings while cloning.

The enhanced clone operations provided by this app are available on the More menu when viewing an issue. A default install will add Clone+ and Clone++ clone operations. However, your administrator may have customized your installation to select what clone operations are available for specific projects including how they are named and behave. The difference between Clone+ and Clone++ is the latter allows you to change the project and issue type of the clone. Both allow you to change other fields before the clone is created.

You will see the user interface similar to creating issues with some additional options for controlling the clone operation.

Target selection

When you use the Clone++ clone operation to clone an issue you can select the target project and issue type in the following dialog:

The following are various scenarios for displaying a specific Target issue type in addition to the configuration by your administrators:

  • When the original issue type exists in the target project, it is displayed.

  • When the original issue type does not exist in the target project, the default issue type of the target project is displayed.

  • When the original issue type does not exist in the target project and default issue type is not configured in the target project, one of the available issue types from the target project is displayed.

Steps

  1. Select a issue you want to clone in your Jira instance.

  2. In the top of the issue, click More > Clone+.

  3. On the Clone page, select values for all the fields as required.

  4. Click Create.
    The issue is cloned as configured and displayed.

 

  • You can add attachments on the fly while cloning an issue. This field is available only when:

    • The global configuration in the instance is set to Allow attachments.

    • The user cloning the issue has permissions to create attachments.

    • The attachment field is not hidden using the field configurations.

  • The Copy links option is displayed only when the an associated link type of the original issue is Relates, Derived, Duplicate, and so on. This option is not displayed when the original issue:

    • is cloned from a different issue, that is, when the associated link type is Clones
      AND/OR

    • does not have any associated link(s)

  • When you clone an issue from a non-JSD project into a JSD project, you can configure the Request type field in the Clone page, only when the respective values are defined for the selected Issue type in the target JSD project. If not, Request Typis not defined in the cloned issue.

Log a request with our support team.

Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.