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 add-ons” under the “Add-ons” category. Search for “Deep Clone”, wait until the entry “Deep Clone for Jira” is shown and proceed to “Install” the add-on.
After having installed the add-on 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 addon 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
In order to clone multiple issues at once, search for those issues using the Jira issue search (e.g. on https://yourcompany.atlassian.net/issues/), filtering the issues that you want to clone. You can then start a bulk-clone by choosing the “Deep Clone: bulk-clone” option in the “Export” drop-down:
Note: If you get a “Forbidden (403)” error, you have selected too many issues (usually > 1000). Please try to select the bulk-clone option with less than 1000 issues.
Now, select the project to clone those issues into. Note that 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. You can use it when trying to clone an epic issue individually:
There’s also a direct link on top of the issue list within the epic:
This will clone the epic including all of its issues into the given project, attaching all issues to the new epic.
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. Note that bulk-clone is not affected by permissions at this time, and all users always have access to bulk-clone.
Navigate to the “Global Permissions” within the Jira System settings. At the bottom, you will find the “Deep Clone for Jira” permission. A user with this permission 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 for all issues within the projects using this permission scheme, no matter how global permissions are configured.
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.
- Comment mentions (e.g. writing “[~user]” in a comment) will still send email notifications (we try to suppress email notifications other than when the clone is created).
- Some ServiceDesk and other custom field types cannot be cloned.
If you encounter any issues, feel free to send us an email at email@example.com. We’ll usually reply within one business day.