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
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.
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:
- Issue links (excluding the “clones” issue links)
- 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.
For commonly used clone actions, you may define presets which will reuse the previously defined clone settings.
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
If you want to clone multiple issues at once, you must do the following:
- Search for those issues using the Jira issue search (e.g. on https://yourcompany.atlassian.net/issues/)
- Filter for the issues that you want to clone
- 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:
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:
- Select the Epic you want to clone
- 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)
- Select “Epic Clone”
- Select a project where the clone should be created
- Configure your clone
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.
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.
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.
- In the post functions tab select “Deep Clone”
- Add the “Deep Clone” post function
- Set any necessary parameters
- 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.
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.
- App data from “Zephyr for Jira Cloud” is not cloned, as the data is stored on the vendor’s servers and not within Jira.
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.