Cloning issues with Deep Clone for Jira:

Deep Clone for Jira stands as the most powerful cloning app for Jira Cloud. If you’ve had prior experience with Deep Clone, you’re familiar with its extensive configuration options. You can choose which Jira fields to clone (e.g., comments, attachments, issue status), use it to migrate a bulk of issues to another project or issue types, and even edit certain fields using the Field Editor during cloning.

While the flexibility of the Clone Dialog offers great customization, it can also introduce complexity. The number of configuration options might slow down the overall cloning process and potentially lead to human error.

To address these challenges, we’ve introduced Deep Clone Presets. With Presets, you can save and reuse clone settings, significantly accelerating cloning tasks and reducing the risk of errors. Presets are available for Single Clones, Bulk Clones, and Epic/Tree Clones.

How to Create a Preset

When you install Deep Clone for Jira, no presets come pre-configured. Therefore, you need to create a preset to utilize this feature effectively. You can create, edit, and manage presets in the “Manage Presets” screen:

Navigate to Your Jira Cloud instance > Apps > Deep Clone > Manage Presets.
Choose the tab corresponding to the clone type you wish to create a preset for (Single Clone, Bulk Clone, Epic/Tree Clone).
Click Create a preset

Different Deep Clone Types

Within the “Manage Presets” screen, you can create new presets for “Single Clones,” “Bulk Clones,” or “Epic/Tree Clones.” These are different types of Clones you can perform with Deep Clone for Jira. All of Deep Clone’s clone types enable you to transfer clones to other projects or issue types and edit fields during the cloning process.

  • Single Clone: Duplicate a single Jira issue.
  • Epic/Tree Clone: Clone an epic along with its larger issue hierarchies while preserving the issue structure.
  • Bulk Clone: Clone up to 100,000 issues simultaneously.

Creating a template Epic for a recurring process

Imagine you work at a large company that regularly onboards new team members, involving a set of standard tasks:

  • Configure Email and Communication Tools
  • Grant Access to Company Systems
  • Review Company Policies and Guidelines
  • Attend New Employee Orientation
  • Clarify Role and Expectations
  • Assign Initial Projects
  • Conduct 30-Day Check-in

For this recurring process, you can create an Onboarding Project and, within it, a template epic with the summary “Onboarding new employee.” Under this epic, you can create child issues for each task necessary for onboarding, like the tasks that are listed above.

Since these tasks may involve different departments, you can either assign templates to different individuals or add a component (HR, IT, Management) to indicate the responsible department. Alternatively, you can create the issues in distinct projects. Later on, we’ll explain how to bulk clone issues across various projects.

In our example, we’ve created an epic and its child issues within the same project. This is what your epic might look like:

Deep Clone for Jira: Clone History

You can also incorporate Jira forms or checklists within your tasks to monitor progress. Deep Clone fully supports cloning most checklists and Jira forms. You can even introduce additional hierarchy levels, such as subtasks or higher-level initiatives, as Deep Clone can clone not only epics but also more extensive issue trees.

Create a Preset for an Epic/Tree Clone

Now, let’s create your preset to ensure that everything gets cloned as desired. As mentioned earlier, follow these steps:

  • Go to Your Jira Cloud instance > Apps > Deep Clone > Manage Presets.
  • Select the Epic/Tree Clone tab to create your preset for cloning this epic.
  • Click Create new preset.

As a first step, you can give your preset a name, such as “Onboarding Process.” If you want to trigger the Epic Clone quickly, check the boxes for “Add as an icon to issue menu” and “Clone immediately.” This way, you can select the preset directly from the action menu without opening the clone dialog.

Deep Clone for Jira: Clone History

In the ensuing dialog, you can determine which fields to clone, which ones to edit, and which to skip. Select the “Onboarding Project” as the target project and “Same as original” as the issue type to retain the hierarchy and different issue types in the target issues. If you work with Subtasks, ensure they’re selected in the Preset Dialog. As a general rule, choose fields based on your issue content and data requirements. For example, if your template issues have attachments, select the appropriate option in order to clone attachments.

Deep Clone for Jira: Clone History

Regarding advanced options, it’s advisable to uncheck “Prefix summary” and “Add clones issue link,” as these are standard Jira options typically unnecessary for recurring processes. On the other hand, it is recommended to keep “Clone other editable fields” and “Clone issue properties” checked. Issue properties are important to clone, if you work with fields coming from other Marketplace apps or Jira features like forms, since they store their data in issue properties. For the parent link, select “Link to cloned parent or else clear” to ensure issues are correctly linked.

Deep Clone for Jira: Clone History

Cloning an Epic with a Preset

Now, you can navigate to the epic you want to clone. Click on the three-dots issue action menu, and you should find the Preset listed (if it’s not visible, make sure you’ve selected “Add as an icon to the issue action menu” in the Preset configuration). Simply click on the Preset, and watch Deep Clone efficiently perform its task.
Setting up a preset reduces the number of clicks required from a minimum of 6 (if no settings are changed in the clone dialog) to just 2 clicks. Furthermore, it eliminates cloning errors since you no longer need to manually configure the correct clone settings; they’re pre-configured and ready to use.

Deep Clone for Jira: Clone History

Cloning Issues from Different Projects with Presets

Now, imagine that the onboarding process is not structured within an Epic but rather consists of tasks scattered across various projects, such as HR, IT, and DEV. The process for creating a preset remains largely the same, but instead of an Epic Clone Preset, you’d create a Bulk Clone Preset under Your Jira Cloud instance > Apps > Deep Clone > Manage Presets > Bulk Clone Preset tab. Ensure you select “Same as original” as the target project and target issue type. For the rest of the Preset configuration, you can follow the instructions under “Create a Preset for an Epic/Tree Clone”.

Since Bulk Clone Presets aren’t triggered from within a Jira issue, the feature to add it to an action menu of an issue is not available here.

Next, consider adding a label like “onboarding-process” to the issues related to the onboarding process. This label will make it easy to filter for these issues. Of course, you can choose any other issue field for filtering purposes. After adding the label, create a “saved filter” for all onboarding issues using Jira’s filter feature (Your Jira Cloud instance > Filters > View all issues).

Now, head to the Deep Clone Bulk Clone feature: Your Jira Cloud instance > Apps > Deep Clone > Bulk Clone. The follow these steps:
Select your onboarding filter as the “source filter”.
Choose “same as original” as the target project.
Fetch the issues, select your preset, and click “clone immediately.”

Voilà! All issues will be swiftly cloned with your preferred settings.

Deep Clone for Jira: Clone History


In conclusion, Deep Clone for Jira Presets are a powerful addition to the app’s capabilities, streamlining and expediting the cloning process for Jira Cloud users. Whether you’re duplicating individual issues, cloning epic hierarchies, or bulk cloning across multiple projects, this feature simplifies repetitive tasks and minimizes the risk of errors. By creating and using presets, you can save time and effort, allowing you to focus on more critical aspects of your work. Download your free trial of Deep Clone for Jira and enjoy efficient, error-free cloning in Jira Cloud with Deep Clone Presets.

Cookie Consent with Real Cookie Banner