Common Permission Scenarios (With Setup Instructions)
This documentation page explains common scenarios for restricting and granting user access to Deep Clone for Jira features. It helps Jira administrators understand how to configure global and project-level permissions to control who can use Single/Epic Clone, Bulk Clone, and Project Clone functionalities.
1. Limit Deep Clone usage to specific users or groups
Restrict Global Permissions:
Navigate to Jira Settings > System > Global Permissions
Remove unwanted users/groups from:
Deep Clone for Jira – Single/Epic Clone
Deep Clone for Jira – Bulk Clone
Deep Clone for Jira – Project Clone
Remove any Project Permissions:
Check your Project Permission Schemes
Ensure users don’t have any Deep Clone project permissions in unwanted projects
2. Show Deep Clone only in selected Jira projects
Remove Global Access:
Go to Jira Settings > System > Global Permissions
Remove all users from
Deep Clone for Jira – Single/Epic Clone
Grant Project-Level Access:
In each project where the Deep Clone button should appear:
Go to Project Settings > Permissions
Add
Deep Clone for Jira – Single/Epic Clone
to the desired roles/groups
3. Certain users should be able to clone projects using templates, even without Jira project creation permissions
Grant Global Permission:
Go to Jira Settings > System > Global Permissions
Ensure the user or group has:
Deep Clone for Jira – Project Clone
No additional Jira project creation permission is required.
4. Only selected users should be able to Bulk Clone work items
Limit Global Permission:
Go to Jira Settings > System > Global Permissions
Restrict
Deep Clone for Jira – Bulk Clone
to specific users or groups
5. Ensure users can only clone using predefined Deep Clone Presets
Go to Jira Settings > Apps > Deep Clone > Restrict Access
Configure as follows:
Check “User-group access”
Check “Allow using Single Clone presets”