Breadcrumbs

Common Permission/Access Scenarios

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 Space Clone (Project Clone) functionalities.

Limit Deep Clone usage to specific users or groups

  • Restrict Global Permissions:

    • Navigate to ⚙️ 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

Show Deep Clone only in selected Jira spaces

  • Remove Global Access:

    • Go to ⚙️ Settings > System > Global Permissions

    • Remove all users from Deep Clone for Jira – Single/Epic Clone

  • Grant Project-Level Access:

    • In each space where the Deep Clone button should appear:

      • Go to Space Settings > Permissions

      • Add Deep Clone for Jira – Single/Epic Clone to the desired roles/groups

Certain users should be able to clone spaces (projects) using templates, even without Jira project creation permissions

  • Grant Global Permission:

    • Go to ⚙️ Settings > System > Global Permissions

    • Ensure the user or group has:

      • Deep Clone for Jira – Project Clone

    No additional Jira project creation permission is required.

Only selected users should be able to Bulk Clone work items

  • Limit Global Permission:

    • Go to ⚙️ Settings > System > Global Permissions

    • Restrict Deep Clone for Jira – Bulk Clone to specific users or groups

Ensure users can only clone using predefined Deep Clone Presets

  • Go to ⚙️ Settings > Marketplace apps > Deep Clone > Restrict Access

  • Configure as follows:

    1. Check “User-group access”

    2. Check “Allow using Single Clone presets”

Let users clone into spaces and instances they don’t have access to

This can be done by cloning with Deep Clone via a workflow post-function or action. The clone is automatically created in the target space or instance when the issue transitions to a configured status, even if users don’t have access to the destination.

If you don’t want cloning to occur on a status change, Deep Clone can also be integrated with Jira Automation.

For step-by-step instructions, see our documentation on setting up Deep Clone post-functions/actions or integrating it with Jira Automation.