The full presentation of the tool's capabilities can be found here: https://support.atlassian.com/jira-software-cloud/docs/understand-project-permissions-and-roles/ |
If after reading you still have problems with managing and granting access rights, submit please a ticket: https://jira.eufus.psnc.pl/projects/JIRASUPP/issues/ |
Permissions are settings within Jira applications that control what users within those applications can see and do. All Jira applications allow a variety of permissions: from whether users can create new projects to whether a user can see a specific type of comment on an issue. These permissions can differ between applications.
There are three types of permissions in Jira applications, and they range from the high-level to granular:
Permissions can be assigned to groups or to project roles/and or issue roles. This diagram illustrates how permissions are assigned to users:
Permission | Can be set by | For more info, see... |
---|---|---|
Global permission | A user with the Jira System administrator permission A user in a group with Admin access | |
Project permission | A user with the Jira System administrator permission A user in a group with Admin access | |
Issue security permission | A user with the Jira System administrator permission A user in a group with Admin access A project admin |
People and groups can be part of more than one role. In the Role column, use the dropdown to select and unselect the roles a person or groups is assigned.
To remove a person or group from a project, select Remove.
Since group membership can only be edited by users with the Administer Jira global permission, project administrators may prefer to assign users, rather than groups, to their project roles. |