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.
We have limited influence on the order of issue keys of the cloned issues.
Some features are not available when cloning between instances.
Cloning Projects
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
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.
Recommended Articles
How to Clone a Project in Jira?
NEW: How to clone a Jira Project from one Instance to another?
How to clone Instance to Instance in Jira?
How to clone an Epic or Initiative in Jira?
How to perform a Post Function Clone in Jira?
How to copy a Project without Issues?