...
| Include Page | ||||
|---|---|---|---|---|
|
Topics
| Table of Contents | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
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.
...
Restricting Access to the App
...
Global Permissions,
Board Administration,
Board Manage & Readonly Permissions.
Global Permissions
Global App Permissions
Global permissions are created automatically when installing the App. There is ongoing issue with Atlassian when on some sporadic cases Global permissions are not properly populated. In this cases, no one can access the App and Jira Global Administrators need to configure it manually.
...
| Note |
|---|
Note: the above applies only to Release Management App you still can’t create/edit release using Jira standard functionality of you are not project admin. |
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.
...
| Note |
|---|
Note: the above applies only to Release Management App you still can’t create/edit components using Jira standard functionality of you are not project admin. |
| Include Page | ||||
|---|---|---|---|---|
|