Skip to main content
Skip table of contents

Restrict Deep Clone Usage

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.

Global Permissions

Project Permissions

Restrict Access

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 > Restrict access.

Deep Clone for Jira Restrict Access configuration screen

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

  1. Check Restrict access to user-groups

  2. Select the project in the drop-down you want to restrict cloning into

  3. Select group(s) that should still be allowed to clone into this project

  4. Save

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

Data Security Policies | App Access Rules

A Jira Organization Administrator can also restrict access for Deep Clone for Jira with data security policy on https://admin.atlassian.com/ under Security > Data security policies. There, it’s possible to create an app access rule to limit access for Deep Clone (or other apps) to specific projects.

What will my users experience?

When the Block app access option is selected, users will no longer see apps in Confluence spaces or Jira projects in which they are blocked, and the apps will behave as though they have been uninstalled. Users will see errors informing them that the app cannot be loaded in macros, links to apps will no longer be accessible, and supporting app functions such as inline dialogues will no longer appear. When Allow app access is selected, apps will appear as normal and all app functions will be available. If you Allow app access for an app that was previously allowed and then blocked, historical data saved by that app in app storage may be out of date or unavailable, depending on the app’s data retention policy.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.