Deep Clone for Jira

Clone a single issue or a bulk of issues into other Jira projects or issue types, clone attachments, comments and other content

Documentation

This is the documentation for the Atlassian Jira app Deep Clone for Jira.

Installation

Head to the settings within Jira. Note that administrator privileges are required to access the settings.

In the menu on the left side, navigate to “Find new apps” under the “apps” category. Search for “Deep Clone”, wait until the entry “Deep Clone for Jira” is shown and proceed to “Install” the app.

Cloning

 

 

After having installed the app from the Atlassian Marketplace, you can start using it right away! Just navigate to a Jira issue of your choice. Then, click on the “Deep Clone” button or the 3-dots-menu and the “Deep Clone” entry on the upper right-hand corner of the issue.

 

The following dialog will appear:

You’re then able to configure how the issue should be cloned. Specify a target project and issue type, along with which other embedded content from the issue should be cloned, including:

  • Attachments
  • Comments
  • Issue links (excluding the “clones” issue links)
  • Votes
  • Watchers
  • Work log

You’ll see in parentheses next to these how many of an embedded type would be cloned, e.g. “Attachments (3)” would show that we’ve detected 3 attachments that would be cloned if the checkbox is activated. For comments and the work log, you can select that the original time the comment was created at will be added to the comment as the first line (since the comments themselves will be shown as being created when you clone the issue).

In the advanced options, you can control some other details that the built-in clone functionality of Jira provides, hence they’re all checked by default. (The intention is that the default settings replicate the default Clone functionality from Jira as much as possible.)

Once you click the “Create and confirm” button, the “create issue” screen will appear where you can confirm the values the issue will be created with. After having confirmed this, you can see how we clone the additional fields and embedded content:

You may close the dialogue at any time without the cloning process to be interrupted. Note however that if you start editing the issue right away, your changes may be overwritten until the cloning process is finished.

Alternatively, you may also choose the “Clone immediately” button to skip the “create issue” screen and clone the issue immediately. However, if the app cannot extract all required fields from the original issue, the button will be greyed out and you’ll have to use the “Create and confirm” button.

Presets

For commonly used clone actions, you may define presets which will reuse the previously defined clone settings.

This is how you create a preset:

  1. Navigate to any Jira issue
  2. Click the 3-dots menu on the upper right-hand corner > Deep Clone
  3. Configure the “single clone” dialogue to match your desired presets
  4. Scroll to the bottom of the dialogue
  5. Enter an arbitrary name for your preset
  6. Click “Add”

For each preset, you can

  • assume the settings (e.g. to review or change the checkboxes before cloning)
  • clone using the “Create and confirm” option
  • clone using the “Clone immediately” option
  • delete the preset

 

 

Bulk Clone

 

 

If you want to clone multiple issues at once, you must do the following:

  1. Search for those issues using the Jira issue search (e.g. on https://yourcompany.atlassian.net/issues/): Jira navigation > Filters > Search issues
  2. Filter for the issues that you want to clone
  3. Start a Bulk Clone by clicking the “Deep Clone: Bulk Clone” button  on the top right next to the “share” and “export” menu. 

Note: On this screen there are two “Export” drop-down menus. One within the issue, the other one above on the right side of the search screen. You find the Bulk Clone option on the top right of the search screen.

4. Now, select the project to clone those issues into.

Note: At the moment, only one project can be selected – if you want to clone the issues into multiple different projects you have to start multiple bulk-clones. The issues will be analyzed for compatibility in the new project and you can proceed with the bulk-clone process with all the options you’ve already seen above:

Epic Clone

A special case of Bulk Cloning is to clone an Epic issue including all of its issues. Since it’s such a common use case, we’ve implemented a dedicated “Epic Clone” feature.

 

 

In order to clone an Epic and all its issues, you must do the following:

  1. Select the Epic you want to clone
  2. Click on the “Deep Clone” button in the “3-dots” menu  (Old Jira Issue View: Click on the “Deep Clone” button next to the share menu)
  3. Select “Epic Clone”
  4. Select a project where the clone should be created
  5. Configure your clone

 

Bulk Edit

When bulk cloning you can bulk edit the clones before they’re created.

  1. Open the Bulk Clone dialogue (Read about bulk cloning in our documentation.)
  2. Click “Clone and bulk edit”
  3. Click “next”
  4.  Add and configure the fields you want to bulk edit. Note: The fields are only edited in the clones. The original issues won’t be changed.
  5. Start bulk clone.

Permissions

By default, all logged-in users can use Deep Clone for Jira. You can restrict permissions either globally or per project. A user has access by either having global permissions or project permissions, they don’t need both permissions.

Global Permissions

Navigate to the “Global Permissions” within the Jira System settings. At the bottom, you will find the “Deep Clone for Jira (Single/Epic Clone)” permission and “Deep Clone for Jira (Bulk Clone) permission. A user with this permissions will be able to access Deep Clone for Jira for all issues in all projects, no matter how project permissions are configured.

Project Permissions

Navigate to the Permission scheme of a project. At the bottom, you will again find the “Deep Clone for Jira” permission. A user with this permission will be able to access Deep Clone for Jira (Single/Epic Clone) for all issues within the projects using this permission scheme, no matter how global permissions are configured.

Note: “Deep Clone for Jira (Bulk Clone)” permission can only be granted globally.

Workflow Post Function

Clones can be triggered automatically when transitioning issues.

To enable that you’ll have to add a Jira post function. How to add a post function is explained in the Atlassian documentation.

  1. In the post functions tab select “Deep Clone”
  2. Add the “Deep Clone” post function
  3. Set any necessary parameters
  4. Publish the updated workflow

Now, a clone is created automatically everytime the adapted transition is executed.

It’s also possible to add several “Deep Clone” post functions.

 

Cloning Sprints

It is possible to clone the sprint-ID with Deep Clone for Jira. In order to do that you just have to mark “Sprint” as checked in the clone dialog.

Note: We are not creating a new sprint in the target project. The same sprint-ID is associated to the cloned issue. 

If you want to link the cloned issues to a new sprint with the same name in the target project, we recommend this as a workaround:

  • Create the new sprint in the target project

  • Filter for the issues you want to bulk clone and navigate to the bulk clone dialogue

  • Select “Clone and bulk edit”

  • Bulk edit the sprint value

Integration with other Marketplace apps/ Atlassian features

 

ProForma

With ProForma you can build forms and checklists in Jira without using custom fields. With Deep Clone it is possible to clone an issue with all of the Pro Forma forms attached to it. This can also be automated using a Deep Clone’s post function on a transition.

You are flexible to decide whether you want to clone a form or not. Just (un)check “Clone issue properties” in the Deep Clone dialog.

 

Tempo Timesheets

You can clone Tempo Timesheet worklogs with Deep Clone. This is how it is implemented:

Logged work is cloned if you select “worklog” in the Deep Clone dialog.

Original estimate is usually cloned (we follow the Atlassian clone function here). If the field “original estimate” is not in the create issue screen, you can prevent cloning it by deselecting “Clone other editable fields (not shown in “Create issue” screen)”

Remaining estimate:

  • If you don’t clone the “worklog” the “remaining estimate” matches the “original estimate” in the cloned issue.
  • If you clone the “worklog” the “remaining estimate” matches the “remaining estimate” in the original issue.

 

Smart Checklist for Jira

It is possible to clone checklists of Smart Checklist for Jira with Deep Clone.

You are flexible to decide whether you want to clone the checklist or not. Just (un)check “Clone issue properties” in the Deep Clone dialog.

Note: Checked items remain checked after cloning.

 

Jira Automation

It is possible to create automation rules for issues that were cloned with Deep Clone for Jira.

If Deep Clone and Automation overwrite each other, you could insert a ‘refetch issue data’ action immediately after the trigger in Automation for Jira. In ‘more options’ you can manually configure a delay which would solve your problem.

Scopes

A Deep Clone for Jira installation requires the following scopes:

  • “Read” is required to get information about the original issues, e.g. project configuration. Deep Clone uses that information to prepare the clone dialog and prevent errors.
  • “Write” enables Deep Clone to create the cloned issues in your instance.
  • “Delete” is needed to remove field content which is not desired, e.g. when you don’t want to clone watchers.
    Deep Clone also uses “delete” to prevent unnecessary notifications when comments are cloned. When a comment is cloned, Jira adds the commenter as a watcher. Deep Clone immediately removes the watcher to prevent that a notification is sent.
  • “Admin” is required to get information about workflows. It also enables Deep Clone to clone issues that cannot be edited by a normal Jira user (e.g. closed issues).
  • “Act as user” is required to clone comments and worklogs, making them appear as if they were added by their original author .

You can read more about scopes in the Atlassian Developer documentation.

Known problems

We try our best to clone issues with as little deviation from the original issue as possible. Unfortunately, due to some limitations of Jira, a few problems remain where we cannot make exact clones of existing issues:

  • Comments and work logs with restricted visibility will not be cloned.
  • While cloning comments, mentions (e.g. writing “[~user]” in a comment) will still send email notifications when cloning the comment. We try to suppress all other email notifications, except for the “issue created” notification.
  • Some ServiceDesk and other custom field types cannot be cloned.

Deep Clone is not compatible with the following Marketplace apps:

  • App data from “Zephyr for Jira Cloud” is not cloned, as the data is stored on the vendor’s servers and not within Jira. It is possible to clone the Zephyr test and the test steps. But the attachments from the steps aren’t cloned.
  • XRay Test Management is currently not supported.
  • Checklists from “Issue Checklist Free” are not cloned.
  • Draw.io diagrams are not cloned successfully. To prevent that a copy of the draw.io diagram is created, uncheck “Clone issue properties”.

Support

Do you have any questions or feedback? Don’t hesitate to get in touch with our support team. We’ll usually reply within one business day.

 

Thanks for using Deep Clone for Jira!