Error formatting macro: appfire-confluence-analytics: java.lang.NullPointerException: Cannot invoke "com.atlassian.confluence.xhtml.api.MacroDefinition.getMacroId()" because "macroDefinition" is null
Skip to end of banner
Go to start of banner

How to clone an entire project - Cloud

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Description

Consider a scenario where you want to create a new Jira project that comprises the same requirements and features of an existing project. Instead of creating all the issues from scratch, you can simply use the Clone Plus for Jira - Bulk Clone feature to copy all the issues from the existing project into a new one. This page explains the steps to create a clone of an entire project.

Steps

An example project Issue tracking is considered as an existing project in this tutorial. All the issues in this project must be cloned to a new project Help desk ticket tracking (for example) in bulk.

  1. Search for all the issues in the existing project using Filters > Advanced issue search in the top horizontal navigation for advanced search or use Switch to basic next to the search bar for basic search.

    The bulk clone action is applied to a maximum of 1000 issues in a project. If a project has more than 1000 issues, the remaining issues are ignored and are not cloned.

  2. Click the Bulk Clone (Clone Plus for Jira) icon at the top right of the page to navigate to the bulk cloning screen.

  3. Select all the issues by selecting the check-box from the first column in the heading in the Step 1 of 3: Choose issues tab.

  4. Click Next to navigate to the next step or Cancel to terminate the bulk clone operation and navigate back to the issue search screen.

  5. Select the following details in the Step 2 of 3: Bulk Clone details tab:


    • Clone operation: The configuration of the selected clone operation is applied to the issues being cloned.

    • Project: The issues are cloned into the selected project.

    • Issue type: The issues being cloned are assigned the selected issue type.

      • You cannot clone a Subtask to the same (subtask) issue type. You notice a warning once you submit the form for cloning. 
      • Images or any form of media added to rich text editor fields such as description, or comments, or environment, are copied to the cloned issue only if Copy attachments is selected. If not, a broken image is displayed in the respective field of the cloned issue. To know more about the support for copying media from text fields to the cloned issue, refer to  JCPP-1332 - Getting issue details... STATUS .

    • Clone options: The values of the options selected here are copied to the respective issues being cloned.

  6. Click Next to navigate to step 3.

  7. Review the Issues selected and Bulk Clone details in Step 3 of 3: Confirmation tab. When ready, click Run Clone to clone the listed issues.

    • The issue list in the Issues selected section is paginated and a maximum of five issues are displayed per page. Click the next > and previous < buttons to navigate to the next and previous pages respectively.
    • You can switch between the tabs at any point during setting up the details for bulk cloning and the details provided in the previous tab are retained.

  8. Click View Clone(s) to view the all the cloned issues in the Search screen.

Refer to Tutorials for more examples

  • No labels