| 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, go navigate to Apps → Manage your apps → Epic Clone settings on the left sidebar to access reach the configuration page for Epic Clone.
...
Access to Epic Clone can be restricted limited to either certain specific projects , or to certain user groups. As said above, by default nothing is selected and By default, the app is available in accessible to all projects and for all user groups.
To restrict access to certain projects, select the projects in the respective field, click on add and save the configuration. The same procedure can be used for groups.
...
The save button only appears when you changed something in the configuration. Selected projects or groups can be removed by clicking on the trash icon next to them.
...
When the save button has been clicked, the following message appears that the new configuration is now , 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 isn’t possible to hide is not feasible to completely conceal the Epic Clone issue action completely if when the app is not available inaccessible in a project or for the user accessing attempting to access the issue.
HoweverNevertheless, the following message appear will be displayed when Epic Clone is not available unavailable in a project but users attempt to open the issue action is opened by users.
...
If Epic Clone is restricted limited to certain specific user groups and an a user not in outside of those groups opens attempts to access the clone dialog, they will encounter the following message appears.
...