Known Limitations

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

• When using Create and confirm, are few limitations are known:

  • The correct work/request type is not preselected. Due to a Jira change, Deep Clone isn’t able to change the work/request type that is pre-selected when using Create and confirm and Jira will pre-select the work/request type. This only applies to company-managed Jira Service Management spaces (projects).

  • The work item creation dialog shows the DateTime field values which Deep Clone pre-fills in UTC timezone instead of the user’s time zone. However, when the user changes the selection they need to choose the value according to their own time zone.

  • If the fields Assignee, Reporter and/or Parent are edited in the Field Editor, the edited values won’t be preselected. However, these values will be set by Deep Clone after creating the work item.

• Deep Clone encounters permission problems when trying to clone into spaces (projects) that have been created using the Custom Space Template feature that is available on Jira Enterprise. This is due to a Jira bug: https://jira.atlassian.com/browse/JRACLOUD-94900

• If “Work Item Links” are set to required in the Field Configuration, Deep Clone can’t clone work item links and can only clone via "Create and confirm" and not via "Clone immediately".

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

• Jira doesn't allow us to modify certain date and time fields or clone work item histories.

• Completed sprints cannot be cloned.

• Some Xray entities cannot be cloned at the moment.

• We have limited influence on the order of work item keys of the cloned work items.

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

Custom issue project/issue type/priority icons not displaying for some users

Custom icons in Jira will only be displayed if the user has Browse projects permission for at least one project, the icon is used in. Read more on the technical background here.

In Firefox, Enhanced Tracking Protection enables Isolate cross-site cookies by default. This blocks the app iframe from using the user's Atlassian session cookie to display custom icons, preventing Jira from verifying if the user has the Browse projects permission. To resolve this, users must disable Enhanced Tracking Protection for Jira, turn off Isolate cross-site cookies in its settings, or add your Jira URL to the exceptions.

Cloning Spaces (Projects)

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

  • Create the space manually and clone all work items using Bulk Clone afterward.

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

• Company-managed Jira Service Management spaces 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 spaces in the Atlassian community.

• Category field can’t be cloned. Due to changes on Atlassian's site, the Category field can normally no longer be changed by third-party apps.

  At the moment, Atlassian is able to unlock the Category field on a customer site basis, which needs to be requested by the site admin to our Product team. This however might have some consequences for data integrity and potentially corrupt the site. Please have your site admin contact Atlassian Support if you need Deep Clone for Jira clone the Category field.

• Cloning work item layouts is currently not possible for Deep Clone:

  • This is a technical limitation of Jira Cloud. You can vote and watch a Jira feature request here.

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

    

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

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

Cloning Work Items Between Instances

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

• Work item links that are targeting an work item 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 work item, the “Clone Sprint ID” option is not supported, as the sprint does not exist on the target instance

Cloning Spaces (Projects) Between Instances

• Project Roles (or the membership to these roles for a space) can only be cloned if a role with the same name exists in the target instance.

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

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