Documentation for JIRA 4.1. Documentation for other versions of JIRA is available too.

Skip to end of metadata
Go to start of metadata

On this page:

Project permissions are created within Permission Schemes, which are then assigned to specific projects.

Project permissions can be granted to:

  • Individual users
  • Groups
  • Project roles
  • Issue roles such as 'Reporter', 'Project Lead' and 'Current Assignee'
  • 'Anyone' (e.g. to allow anonymous access)
  • A (multi-)user picker custom field.
  • A (multi-)group picker custom field. This can either be an actual group picker custom field, or a (multi-)select-list whose values are group names.

The following table lists the different types of project permissions and the functions they secure. Note that project permissions can also be used in workflow conditions.

Project Permission

Explanation

Add Comments

Permission to add comments to issues. Note that this does not include the ability to edit or delete comments.

Administer Projects

Permission to administer a project in JIRA. This includes the ability to edit project role membership, project components, project versions and some project details ('Project Name', 'URL', 'Project Lead', 'Project Description').

Assign Issues

Permission to assign issues to users. (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 above).

Browse Projects

Permission to browse projects, use the Issue Navigator and view individual issues (except issues that have been restricted via Issue Security). Users without this permission will not know that the project or its issues exist.

Close Issues

Permission to close issues. (This permission is useful where, for example, developers resolve issues and testers close them). Also see the Resolve Issues permission.

Create Attachments

Permission to attach files to an issue. (Only relevant if attachments are enabled). Note that this does not include the ability to delete attachments.

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 sub-tasks (if sub-tasks are enabled).

Delete All Attachments

Permission to delete any attachments, regardless of who added them.

Delete All Comments

Permission to delete any comments, regardless of who added them.

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.

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.

Delete Own Attachments

Permission to delete attachments that were added by the user.

Delete Own Comments

Permission to delete comments that were added by the user.

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.

Edit All Comments

Permission to edit any comments, regardless of who added them.

Edit All Worklogs

Permission to edit any worklog entries, regardless of who added them. (Only relevant if Time Tracking is enabled). Also see the Work On Issues permission.

Edit Issues

Permission to edit issues (excluding the 'Due Date' field — see the Schedule Issues permission). Includes the ability to convert issues to sub-tasks and vice versa (if sub-tasks 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). Note that all edits are recorded in the Issue Change History for audit purposes.

Edit Own Comments

Permission to edit comments that were added by the user.

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.

Link Issues

Permission to link issues together. (Only relevant if Issue Linking is enabled).

Manage Watcher List

Permission to manage (i.e. view/add/remove users to/from) the watcher list of an issue.

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.

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.

Resolve Issues

Permission to resolve and reopen issues. This also includes the ability to set the 'Fix For version' field for issues. Also see the Close Issues permission.

Schedule Issues

Permission to schedule an issue — that is, set and edit the 'Due Date' of an issue.

Set Issue Security

Permission to set the security level on an issue to control who can access the issue. Only relevant if issue security has been enabled.

View Version Control

Permission to view the version control information (e.g. CVS, Subversion, FishEye, etc) for an issue. Note that for CVS, to view the Version Control information the project needs to be associated with at least one Repository.

View Voters and Watchers

Permission to view the voter list and watcher list of an issue. Also see the Manage Watcher List permission.

Work On Issues

Permission to log work against an issue, i.e. create a worklog entry. (Only relevant if Time Tracking is enabled).

Permission Schemes

What is a Permission Scheme?

A permission scheme is a set of user/group/role assignments for the project permissions listed above. Every project has a permission scheme. One permission scheme can be associated with multiple projects.

Why Permission Schemes?

In many organisations, multiple projects have the same needs regarding access rights. (For example, only the specified project team may be authorised to assign and work on issues).

Permission schemes prevent having to set up permissions individually for every project. Once a permission scheme is set up it can be applied to all projects that have the same type of access requirements.

Creating a Permission Scheme

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
  3. On the panel on the left, under the title 'Schemes', click the link labelled 'Permission Schemes'.
  4. This will display the 'Permission Schemes' page. This page lists all of the Permission Schemes that JIRA currently has. Click the 'Add Permission Scheme' link.
  5. In the 'Add Permission Scheme' form, enter a name for the scheme, and a short description of the scheme. Click the 'Add' button.
  6. You will return to the 'Permission Schemes' page which now contains the newly added scheme.

Adding Users, Groups or Roles to a Permission Scheme

  1. On the panel on the left, under the title 'Features', click the link labelled 'Permission Schemes'.
  2. Click the 'Permissions' link or on the name of the Permission Scheme to show a list of permissions
  3. Click the 'Add' link in the 'Operations' column.
  4. This will display the 'Add Permission' page. After selecting one or more permissions to add and who to add the selected permissions to, click the 'Add' button. The users/groups/roles will now be added to the selected permissions. Note that project roles are useful for defining specific team members for each project. Referencing project roles (rather than users or groups) in your permissions can help you minimise the number of permission schemes in your system.
  5. Repeat the last 2 steps until all required users/groups/roles have been added to the permissions.
  6. To delete a user/group/role from a permission click the 'Delete' link in the "Users / Groups / Roles" column.

Associating a Permission Scheme with a Project

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
  3. A list of projects is displayed
  4. Select the project you want by clicking on the project name. This will display the project details
  5. Click the 'select scheme' link beside the Permission Scheme caption.
  6. This will bring up a list of Permission Schemes. Select the Permission Scheme that you want to associate with this project.
  7. Click the 'Associate' button to associate the project with the permission scheme.

Deleting a Permission Scheme

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
  3. On the panel on the left, under the title 'Features', click the link labelled 'Permission Schemes'.
  4. This will display the 'Permission Schemes' page. This page lists all the Permission Schemes that are currently defined in your JIRA system. Click the 'Delete' link for the scheme that you want to delete.
  5. A confirmation screen will appear. To delete click 'Delete' otherwise click 'Cancel'.
  6. The scheme will be deleted and all associated projects will be automatically associated with the Default Permission Scheme. (Note that you cannot delete the Default Permission Scheme.)

Copying a Permission Scheme

  1. Log in as a user with the 'JIRA Administrators' global permission.
  2. Bring up the administration page by clicking either the 'Administration' link on the top bar or the title of the Administration box on the dashboard.
  3. On the panel on the left, under the title 'Features', click the link labelled 'Permission Schemes'.
  4. This will display the 'Permission Schemes' page. This page lists all of the Permission Schemes that JIRA currently has. Click the 'Copy' link for the scheme that you want to copy.
  5. A new scheme will be created with the same permissions and the same users/groups/roles assigned to them.

Additional Resources

  • Permission scheme overview tutorial video - Watch this short tutorial video to see how to set up a new permission scheme to control which users can perform which operations on an issue. Please note the JIRA version of the tutorial video before watching.