| Info |
|---|
This page outlines the level of permissions exists to restrict access to the App and its functionality. But also additional permissions App create to let non-admin access to some Jira functionality, thus letting admins delegate some controls to individuals. |
| Table of Contents | ||
|---|---|---|
|
...
Restricting Access to the App
There are three levels of Apps permissions, namely
...
Global permissions are good to decide who can view/access the application. But once you can view/access you can create any Release Board with Projects that are available to you in order to manage releases. Some companies want to restrict such flexibility to have a limits subset of approved release boards. Therefore, we created a special permission - [Release Management - New Release Board Creation] - that allows to specify users/groups that could create boards in Application.
Classic Components Management Permissions
In Jira by default Components belong to Projects and could be managed by Project Admins only. This overcomplicates cross-project component management. Therefore, most of the Partner Apps that have a functionality for cross-project component management are making all the changes in App-context allowing to override Project Admin permissions.
To give Jira Global Administrators control over it we created a special permission - [Release Management - Global Classic Component Management] - that allows to specify users/groups that could change Components from Release Management w/o being Admin for corresponding Jira Projects. The scope of such permission applies only to the projects listed for the board.
Board Administration Permissions
...
Users of projects in board
This option grants Board Manage, Readonly permission to all users who have permission to view projects added to the board.
Users of projects
Board Manage, Readonly permission is granted to all users who have permissions to browse selected projects.
Users and groups
Board Manage, Readonly permission is granted to specified Jira Users and groups.
Permissions for Non-Admins
Versions/Releases Management Permissions
TBD
Classic Components Management Permissions
In Jira by default Components belong to Projects and could be managed by Project Admins only. This overcomplicates cross-project component management. Therefore, most of the Partner Apps that have a functionality for cross-project component management are making all the changes in App-context allowing to override Project Admin permissions.
To give Jira Global Administrators control over it we created a special permission - [Release Management - Global Classic Component Management] - that allows to specify users/groups that could change Components from Release Management w/o being Admin for corresponding Jira Projects. The scope of such permission applies only to the projects listed for the board.