Permissions
| 
PDF |
From version 1.2, you can secure various functions (for example adding comments or browsing projects) via the
permissions system. Using the permissions system you can configure exactly who can access JIRA, and exactly who
can do what within JIRA.
Each permission has a permission type (see below for table) and a group to which it applies (or it can apply to
everyone).
Anonymous permissions can be created. To create an anonymous permission, set the group to "Anyone". For example
creating an anonymous Browse Project permission for a particular project will mean that anyone accessing JIRA can
browse that project.
There are two types of permissions, global permissions and project specific permissions.
There are some permissions which are system wide. These are known as global permissions and
apply to every project and are edited via "Global Permissions" in administration
interface.
These permissions are non project specific and generally refer to the administration of JIRA itself. Examples of
global permissions are 'JIRA Administrators' which allows people to administer JIRA and 'JIRA Users' which allows people to user JIRA
This table lists the different global permissions and what functions they secure.
| Permission Type | Explanation |
| JIRA Administrators |
Permission to administer this installation of JIRA. |
| JIRA Users |
Permission to log into JIRA. Note that
these 'users' cannot actually do anything other than login and logout without
other permissions. |
| Browse Users |
Permission to allow the browsing of all the users in the system in a popup screen. Used for selecting usernames |
| Create Shared Filter |
Permission to allow user to share a filter globally or with groups of users. |
| Manage Group Filter Subscriptions |
Permission to allow user to manage (create and delete) group filter subscriptions. |
|
Project specific permissions
| |
| | |
All other permissions are Project specific permissions and are created using Permission Schemes which are then assigned to projects
This table lists the different types of permissions and what functions they secure.
| Permission Type | Explanation |
| Project Administrators |
Permission to administer a project in JIRA |
| Browse Project |
Permission to browse projects, use the Issue
Navigator and view individual issues. |
| Create Issue |
Permission to create issues. Note these
users cannot create attachments without Edit Issue permission. |
| Edit Issue |
Permission to edit issues and manage attachments. Note these users cannot delete attachments without the
Delete Issue permission.
All updates are saved in the issue change history, hence you will usually want to give this permission to
any groups with the Create Issue permission (perhaps the only exception to this is if you give everyone
the ability to create issues - you then want to think carefully whether you want to give everyone the
ability to edit too).
|
| Move Issue |
Permission to move issues from one project to another. Note the user can only move issues to a project they have create permission for |
| Assign Issue |
Permission to assign issues to other users.
(See also Assignable User permission below) |
| Assignable User |
Permission to be assigned issues. Note these users cannot necessarily assign issues to other users,
that requires Assign Issue permission.
This permission will usually include your developers.
|
| Resolve Issue |
Permission to resolve and reopen issues.
This also includes the ability to set the FixFor version for issues. |
| Close Issue |
Permission to close issues. Often useful where your developers resolve issues, and a QA department closes them |
| Add Comments |
Permission to add comments to issues. Note
that these users cannot delete comments (see Delete Issue permission). |
| Delete Issue |
Permission to delete issues, comments and
attachments. Think carefully about which groups you assign this permission
to - usually it will just be for administrators of the system. |
| Work On Issue |
Permission to log work done against an issue. Only useful if time tracking is turned on. |
| Link Issues |
Permission to link issues together and create linked issues. Only useful if issue linking is turned on. |
| Create Attachments |
Permission to attach files to an issue. |
| Create Attachments |
Permission to attach files to an issue. |
| Set Issue Security |
Permission to set the security level on issue to control who can access the issue.(Enterprise Edition only) |
|
What is a Permission Scheme
| |
| | |
A Permission Scheme is a set of user permissions that can be applied to any project. This prevents having to duplicate permissions for different projects.
Once a scheme is set up it can be applied to as many projects as you need
In the majority of cases a lot of projects will have the same needs as regards permission. i.e The same people need to have the same access rights for more than one project.
With permission schemes you only need to set the scheme up once and then it can be applied to as many projects as you want, giving all these projects the exact same permissions
There will of course be times when different projects will require a different set of permissions. e.g you might only want a certain department to have access to this project if it is a departmental project.
In this case all you need to do is add a new permission scheme for this or any other project
|
Creating a Permission Scheme
| |
| | |
- Login as a user with global administrator access.
-
Bring up the administration page by clicking either on the "Administration" link on the top bar or the title of the
Administration box on the dashboard:
-
On the panel on the left, under the title "Features", click on the link labelled "Permission Schemes".
-
This will display the "Permission Schemes" page. This page lists all of the Permission Schemes that JIRA currently has. Click on the "Add Permission Scheme" link.
-
In the "Add Permission Scheme" form, enter a name for the scheme, and a short description of the scheme. Click on the "Add" button.
-
You will return to the "Permission Schemes" page which now contains the newly added scheme.
|
Assigning a Permission Scheme to a Project
| |
| | |
- Login as a user with global administrator access.
-
Bring up the administration page by clicking either on the "Administration" link on the top bar or the title of the
Administration box on the dashboard:
-
A list of projects is displayed
-
Select the project you want by clicking on the project name. This will display the project details
-
Click on the "select scheme" link beside the Permission Scheme caption.
-
This will bring up a list of Permission Schemes. Select the Permission Scheme that you want to associate with this project.
- Click the "Associate" button to associate the project with the permission scheme.
|
Adding Users/Groups to a Permission
| |
| | |
-
On the panel on the left, under the title "Features", click on the link labelled "Permission Schemes".
-
Click on the "Permissions" link or on the name of the Permission Scheme to show a list of permissions
-
Click the "Add" link in the Operations column of the Permissions table.
-
This will display the "Add Permission" page. After selecting the appropriate option,
and filling in any required information for that option, click the "Add" button. The users/groups will now be added to that permission
-
Repeat the last 2 steps until all required users/groups have been added to this permission
-
To delete a user/group from a permission click on the "Del" link in the "groups" column
|
Deleting a Permission Scheme
| |
| | |
- Login as a user with global administrator access.
-
Bring up the administration page by clicking either on the "Administration" link on the top bar or the title of the
Administration box on the dashboard:
-
On the panel on the left, under the title "Features", click on the link labelled "Permission Schemes".
-
This will display the "Permission Schemes" page. This page lists all of the Permission Schemes that JIRA currently has. Click on the "Del" link for the scheme that you want to delete.
-
A confirmation screen will appear. To delete click "Delete" otherwise click "Cancel".
- The scheme will be deleted and all associated projects will be associated to the default permission scheme.
**Note that you cannot delete the default permission scheme.
|
Copying a Permission Scheme
| |
| | |
- Login as a user with global administrator access.
-
Bring up the administration page by clicking either on the "Administration" link on the top bar or the title of the
Administration box on the dashboard:
-
On the panel on the left, under the title "Features", click on the link labelled "Permission Schemes".
-
This will display the "Permission Schemes" page. This page lists all of the Permission Schemes that JIRA currently has. Click on the "Copy" link for the scheme that you want to copy.
-
A new scheme will be created with the same permissions and the same users/groups assigned to them.
