Managing Permissions and Access in Deep Clone for Jira

This page explains how to configure permissions and access to Deep Clone for Jira features. Learn how to grant or restrict user access to specific cloning actions like Single Clone, Bulk Clone, and Project Clone.

We're planning to improve permission management in future versions of Deep Clone for Jira. If you have feedback or suggestions, please contact us.

Overview: Key Features and Their Permission Controls

This table provides an overview of key Deep Clone for Jira features, including how to configure or restrict access to each feature, who can make these changes, and the default permission settings after installation.

Feature	How to Configure/ Restriction Method	Configurable by	Default setting
Single Clone Epic/Tree Clone	Global Permissions > “Deep Clone for Jira - Single/Epic Clone” OR Project Permissions > “Deep Clone for Jira - Single/Epic Clone”	Jira Admin Project Admin	Global Permission: Granted to all users Project Permission: Disabled
Bulk Clone	Global Permissions > “Deep Clone for Jira - Bulk Clone”	Jira Admin	Granted to all users
Available target projects in the Clone Dialog	Read more about how to restrict target projects	Jira Admin	By default, users can clone into any project where they have the Browse Projects permission.
Project Clone (Basic)	Global Permissions > “Deep Clone for Jira - Project Clone”	Jira Admin	Granted to Jira Administrator
Advanced Project Clone	Learn how to set up the Advanced Project Clone	Jira Admin	Needs initial setup
Instance Clone	Learn how to set up the Instance Clone	Jira Admin	Needs initial setup
Deep Clone Post-Function	All users that can set up standard post-functions can also set up Deep Clone post-functions.	Jira Admin Project Admin who can edit workflows	n/a
Presets	Can be created by all users. Additional settings for Jira Admins: Jira Settings > Apps > Deep Clone > Restrict Access Allow cloning from Presets for users who don’t have the needed Project Permission.	Jira Admin Project Admin Jira User	Granted to all Jira users
Restrict cloning comments, work logs and/or attachments	Learn how to restrict cloning comments, work logs and/or attachments	Jira Admins	By default, comments, work logs and/or attachments can be cloned
Clone History	n/a	n/a	n/a Jira users can see all clone jobs they started themselves in the selected time frame. Jira Admins can see all clone jobs that run on the instance in the selected timeframe.

Read more about the available permission options

Overview: Key Features and Their Permission Controls