Documentation for JIRA 4.4. Documentation for other versions of JIRA is available too.
Project permissions are created within Permission Schemes, which are then assigned to specific projects.
Project permissions can be granted to:
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.
On this page:
Project Permissions |
Explanation |
---|---|
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'). |
Browse Projects |
Permission to browse projects, use the Issue Navigator and view individual issues (except issues that have been restricted via Issue 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 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 (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 'View Issue' page. |
Issue Permissions |
Explanation |
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). |
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 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 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. |
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. |
Link Issues |
Permission to link issues together. (Only relevant if Issue Linking is enabled). |
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. |
Voters & Watchers Permissions |
Explanation |
Manage Watcher List |
Permission to manage (i.e. view/add/remove users to/from) the watcher list of an issue. |
View Voters and Watchers |
Permission to view the voter list and watcher list of an issue. Also see the Manage Watcher List permission. |
Comments Permissions |
Explanation |
Add Comments |
Permission to add comments to issues. Note that this does not include the ability to edit or delete comments. |
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. |
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. |
Attachments Permissions |
Explanation |
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. |
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 |
Explanation |
Work On Issues |
Permission to log work against an issue, i.e. create a worklog entry. (Only relevant if Time Tracking is enabled). |
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 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 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 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. |
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.
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.
See also Minimising the number of Permission Schemes and Notification Schemes.