Standard permissions in Jira Service Management
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
In Jira Service Management, project administrators are allowed to change permissions. You do not need to be a Jira administrator with global privileges to modify permissions schemes in your service projects.
This page shows the permission configuration for a standard Company Managed Jira Service Management permission scheme. If you are using a Team-managed project, please refer to Overview of permissions in team-managed service projects.
- To see an overview of how permissions are set up for a service project, see Jira Service Management permissions.
- If you want to customize the permission scheme, make sure that the mandatory permissions are assigned to the roles. See Using custom permission schemes.
- If you run into permission-related problems, see Resolve permission scheme errors in Jira Service Management.
Project Permissions | Users / Groups / Project roles | Explanation | |
---|---|---|---|
Administer Projects | Project Role (Administrators) | Permission to administer a project. This includes the ability to edit project roles, components, versions and some project details ('Project Name', 'URL', 'Project Lead', 'Project Description'). | |
Browse Projects | Permission to browse projects, use the Issue Navigator and view individual issues (except issues that have been restricted via issue-level security. Many other permissions are dependent on this permission, e.g. the 'Work On Issues' permission is only effective for users who also have the 'Browse Projects' permission. | ||
| |||
View Development Tools | Permission to view the development information for an issue, which displays information from Bitbucket Cloud, Bitbucket Server, GitHub, Fisheye, Crucible and Bamboo, if Jira is integrated with development tools. For older versions of Bitbucket Server (known as Stash) and Fisheye or for Subversion and CVS, this grants permission to view the integrated development tools for an issue, in the 'Commits' and 'Source' tabs. Note that for CVS, to view the related source code commits, the project needs to be associated with at least one integrated tool. | ||
View (Read-Only) Workflow | Permission to view the project's 'read-only' workflow when viewing an issue. This permission provides the 'View Workflow' link against the 'Status' field of the issue view. | ||
Issue Permissions | Users / Groups / Project roles | Explanation | |
Create Issues | Permission to create issues in the project. (Note that the Create Attachments permission is required in order to create attachments.) Includes the ability to create subtasks (if subtasks are enabled). | ||
Edit Issues | Permission to edit issues (excluding the 'Due Date' field — see the Schedule Issues permission). Includes the ability to convert issues to subtasks and vice versa (if subtasks are enabled). Note that the Delete Issue permission is required in order to delete issues. The Edit Issue permission is usually given to any groups or project roles who have the Create Issue permission (perhaps the only exception to this is if you give everyone the ability to create issues — it may not be appropriate to give everyone the ability to edit too). | ||
Transition Issues | Permission to change the status of an issue. | ||
Schedule Issues | Permission to schedule an issue — that is, to edit the 'Due Date' of an issue. In older versions of Jira this also controlled the permission to view the 'Due Date' of an issue. | ||
Move Issues | Permission to move issues from one project to another, or from one workflow to another workflow within the same project. Note that a user can only move issues to a project for which they have Create Issue permission. | ||
Assign Issues | Permission to assign issues to users. Also allows autocompletion of users in the Assign Issue dropdown. (See also Assignable User permission below) | ||
Assignable User | Permission to be assigned issues. (Note that this does not include the ability to assign issues; see Assign Issue permission). | ||
Resolve Issues | Permission to resolve issues in the workflow and reopen issues. This also includes the ability to set the 'Fix For version' field for issues. Also see the Close Issues permission. | ||
Close Issues | Permission to close issues in the workflow. (This permission is useful where, for example, developers resolve issues and testers close them). Also see the Resolve Issues permission. | ||
Modify Reporter | Permission to modify the 'Reporter' of an issue. This allows a user to create issues 'on behalf of' someone else. This permission should generally only be granted to administrators. | ||
Delete Issues | Permission to delete issues. Think carefully about which groups or project roles you assign this permission to; usually it will only be given to administrators. Note that deleting an issue will delete all of its comments and attachments, even if the user does not have the Delete Comments or Delete Attachments permissions. However, the Delete Issues permission does not include the ability to delete individual comments or attachments. | ||
Link Issues | Permission to link issues together. (Only relevant if Issue Linking is enabled). | ||
Set Issue Security | Permission to set the security level on an issue to control who can access the issue. | ||
Voters & Watchers Permissions | Users / Groups / Project Roles | Explanation | |
View Voters and Watchers | Permission to view the watcher and voter list of an issue. | ||
Manage Watcher List | Permission to manage (i.e. view/add/remove users to/from) the watcher and voter list of an issue. | ||
Comments Permissions | Explanation | ||
Add Comments | Permission to add comments to issues. Note that this does not include the ability to edit or delete comments. | ||
Edit All Comments | Permission to edit any comments, regardless of who added them. | ||
Edit Own Comments | Permission to edit comments that were added by the user. | ||
Delete All Comments | Permission to delete any comments, regardless of who added them. | ||
Delete Own Comments | Permission to delete comments that were added by the user. | ||
Attachments Permissions | Users / Groups / Project Roles | Explanation | |
Create Attachments | Permission to add file attachments to an issue. (Only relevant if attachments are enabled). Note that this does not include the ability to delete attachments. | ||
Delete All Attachments | Permission to delete any attachments, regardless of who added them. | ||
Delete Own Attachments | Permission to delete attachments that were added by the user. | ||
Time Tracking Permissions | Users / Groups / Project Roles | Explanation | |
Work On Issues | Permission to add work in the worklog against an issue, i.e. create a worklog entry. (Only relevant if time tracking is enabled). | ||
Edit Own Worklogs | Permission to edit worklog entries that were added by the user. (Only relevant if time tracking is enabled). Also see the Work On Issues permission. | ||
Edit All Worklogs | Permission to edit any worklog entries, regardless of who added them. (Only relevant if time tracking is enabled). | ||
Delete Own Worklogs | Permission to delete worklog entries that were added by the user. (Only relevant if time tracking is enabled). Also see the Work On Issues permission. | ||
Delete All Worklogs | Permission to delete any worklog entries, regardless of who added them. (Only relevant if time tracking is enabled). Also see the Work On Issues permission. |