| Info |
|---|
First of all, we have to mention that the app always did and will continue to respect the Jira permissions a user has. If users don’t have the The application consistently upholds Jira permissions for users. If a user lacks create permission in a project, they won’t will not be able to clone to that project using Epic Clone. The app settings page described on this page is located in the Jira system administration and thus can only be accessed by , as detailed here, is situated within Jira system administration, exclusively accessible to Jira administrators. |
Epic Clone is available for all users by default
By default, Epic Clone is available and intended to be used by readily accessible to all users in your instance. It can save users time when creating issues and is useful in many cases and for many different roles in your organisation. However, there might be cases where the functionality shall be limited to certain within your instance, aiming to streamline issue creation and cater to various roles across your organization. While it proves beneficial in numerous scenarios, there may arise situations where its usage needs restriction to specific projects or user groups. That is why we introduced the To address this need, we have implemented app permission settings tailored for Jira administrators.
How Jira admins can access the app settings page
As a Jira administrator, navigate to Apps → Manage your apps → Epic Clone on the left sidebar to reach the configuration page for Epic Clone.
...
What Jira admins can configure on the app settings page
Access to Epic Clone can be limited to specific projects or user groups. By default, the app is accessible to all projects and user groups.
To restrict access, navigate to the permission tab and enable the corresponding toggle. You can then choose projects and user groups on separate tabs. Under the project tab, pick a project from the list and include it in the table by clicking the add button.
If restrictions are in place but no projects or groups are specified, the app will still be accessible to all users across all projects.
For a project, you can specify whether attachment cloning should be allowed within that project. If the toggle is turned off, it will prevent the cloning of attachments using Epic Clone, even if the app is accessible in that project.
...
A "Save" button will only be displayed if changes have been made to the configuration. Click on it to save your settings.
Once the "Save" button has been clicked, a message will appear confirming that the new configuration has been successfully saved.
...
How does it look like when access to Epic Clone is denied
Unfortunately, it is not feasible to completely conceal the Epic Clone issue action when the app is inaccessible in a project or for the user attempting to access the issue.
Nevertheless, the following message will be displayed when Epic Clone is unavailable in a project but users attempt to open the issue action.
...
If Epic Clone is limited to specific user groups and a user outside of those groups attempts to access the clone dialog, they will encounter the following message.
...