By default, Deep Clone Global Permissions are set to public.
We're bound to the default permissions, as those are set by Jira. You can rest assured that only issues that users have access to can be cloned using Deep Clone for Jira, no matter how you set the global permissions.
You can restrict or extend permissions either globally or per project.
A user has access by either having global permissions or project permissions, they don’t need both permissions.
Deep Clone for Jira supports restricting access without changing Jira user groups.
You can configure Deep Clone for Jira specific restriction under Apps > Manage Apps > Deep Clone > Restrict access.
If Restrict access is enabled, but no projects are configured, no user will be able to select a target project.
Restrict Cloning Into Certain Projects
Check Restrict access to user-groups
Select the project in the drop-down you want to restrict cloning into
Select group(s) that should still be allowed to clone into this project
Users need to have the “Create issue” permission for this project in order to be able to Deep Clone into it, regardless of the “Restrict access” settings below.
Restrict Other Deep Clone Features
Disable cloning attachments
Disable cloning comments
Disable cloning work logs