Known Limitations

There are known limitations affecting certain Deep Clone features. Click on the links below to get more information.

• Create and confirm doesn’t preselect the correct issue/request type

Due to a Jira change, Deep Clone isn’t able to change the issue/request type that is pre-selected when using Create and confirm and Jira will pre-select the issue/request type. This only applies to company-managed Jira Service Management projects.

• Some custom fields cannot be cloned, due to technical constraints.

• Jira doesn't allow us to modify certain date and time fields.

• Completed sprints cannot be cloned.

• Some Xray entities cannot be cloned at the moment.

• We have limited influence on the order of issue keys of the cloned issues.

• Some Zephyr entities aren't cloned at the moment.

Cloning Projects

• Team-managed projects and company-managed board configurations can only be cloned when the Advanced Project Clone is enabled. If you don’t want to enable the Advanced Project Clone, you can use the following workarounds:

  • Create the project manually and clone all issues using Bulk Clone afterward.

  • Follow these instructions to add boards after cloning the project.

• Company-managed Jira Service Management projects cannot be cloned entirely, and the following entities don’t get cloned:

  • Request types, Forms, and External resources

  • Customer permissions and notifications, language support, email settings

  • Portal, widget, and chat settings

  • Knowledge base links and SLA settings

• Cloning Jira automation rules is not possible at the moment. You can read more about sharing automation rules across projects in the Atlassian community.

• Cloning issue layouts

  • Cloning issue layouts is currently not possible for Deep Clone.

  • While we clone issue screens, it is not possible to clone the issue layout you have configured in one project to another project.
    You can copy the layout manually (in company-managed projects) to your target project using the Jira function under Project settings > Layout > Edit issue layout > Copy issue layout.

    

We are not able to clone issue layouts because the issue layout is not accessible via REST API. You can vote and comment to let Atlassian know if you need this feature.

• When cloning projects across instances boards can’t be cloned, due to limitations of the Jira API.

Cloning Between Instances

• Create and confirm cannot be used due to technical limitations, only “Clone Immediately” is available

• Issue links that are targeting an issue that is not being cloned to the other instance will be added as “Web Links”

• Confluence links will also be added as “Web Links”

• When cloning the sprint of an issue, the “Clone Sprint ID” option is not supported, as the sprint does not exist on the target instance

---

Top Features

• User Permissions
• Advanced Project Clone
• Clone and Edit With Jira Expressions
• Instance Clone
• Looping Transitions & Webhooks
• Deep Clone for Jira REST API
• Project Clone
• Automation for Jira via Workflows
• Post Function Clone
• Bulk Clone
• Epic/Tree Clone

Explore more codefortynine apps

• Version Sync for Jira
• External Data for Confluence
• Comment History Log for Jira
• External Data for Jira Fields
• Comment Custom Fields for Jira
• Deep Clone for Jira
• Snipe-IT for Jira
• Dynamic Custom Fields for Jira
• Advanced Bulk Edit for Jira
• Slack for Confluence
• Google Calendar for Confluence
• Merge Agent for Jira
• Quick Filters for Jira Dashboards
• Get Started
• Easy Confluence Gadget for Jira Dashboards
• Prime Custom Fields for Jira

Please note that there may be more limitations. We cannot guarantee that all other details of a cloned project get cloned as expected, and cannot be made liable for discrepancies between original and cloned projects.

If you discover any other limitations, please contact us so we can improve Deep Clone or add them here.