JIRA

Install

Admin

Use

	JIRA Administrator's Guide Introduction Getting Help Look and Feel Logo, Colours and Timezone Configuring the default Language Configuring the default Issue Navigator Configuring the default Dashboard Overview of Dashboard Portlets Enabling Portlets and Other Plugins Editing the Announcement Banner Enabling Logout Confirmation Email Email Overview Creating a Notification Scheme Customising Email Content Creating Issues & Comments from Email SMTP configuration User Management Managing Users Managing Groups Managing Project Roles Migrating from Groups to Project Roles Enabling public signup and CAPTCHA Integrating JIRA with LDAP Integrating JIRA with Crowd Configuring Trusted Applications Security Overview Global permissions Project permissions Permission Schemes Creating a Permission Sch.. Adding Users, Groups or R.. Associating a Permission .. Deleting a Permission Sch.. Copying a Permission Sche.. Issue security Project Management Defining a Project Assigning members to Project Roles Defining Project Components Defining Project Versions Creating Release Notes for a Version Configuring Project Keys Configuring Fields and Screens Overview Defining 'Resolution' field values Defining 'Priority' field values Defining 'Status' field values Defining 'Issue Type' field values Associating Issue Types with Projects Translating Resolution/Priority/Status/Type Configuring field behaviour Configuring rich-text renderers Associating behaviour with Issue Types Placing fields on screens Associating screens with Issue Operations Associating screens with Issue Types Creating & configuring Custom Fields Custom Field Overview Adding Custom Fields Configuring Custom Fields Configuring Workflow Workflow Activating Workflow Events Importing from Other Systems Importing from Bugzilla Importing from Mantis Importing from FogBugz Importing from Excel/CSV Moving or Archiving Individual Projects Overview Archiving a project Merging JIRA instances Splitting JIRA instances Integrating with Source Control Integrating with CVS and ViewCVS Integrating with Subversion Integrating with Perforce Integrating with ClearCase Integrating with FishEye Configuration Options & Settings Global Settings Enabling Issue Linking Enabling Sub-tasks Enabling Trackback linking Enabling Time Tracking Enabling File Attachments Enabling Thumbnails for Attachments Server Administration Indexing & Search Backing up Data Automated Backups Restoring Data Database Integrity Checker Increasing memory Performance Tips Database Indexing Precompile JSP pages Logging and Profiling Thread Dump Downgrading (Ent to Pro) Downgrading (Ent to Std) Downgrading (Pro to Std) Using robots.txt with Search Engines Appendix A - Extending JIRA Extension Overview Listeners Services Jelly tags JIRA Toolkit Customising Text Developer Guides JIRA Plugins JIRA RPC Overview Creating a SOAP Client Creating an XML-RPC Client Creating Custom Field Types Custom Workflow Elements Creating new Portlets Creating new Reports More.. JIRA Source Building JIRA from source API Documentation

Project permissions

PDF

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' (JIRA Enterprise Edition only)
'Anyone' (eg. 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, in JIRA Professional and Enterprise editions, project permissions can also be used in workflow conditions.

Project Permission	Explanation
Administer Projects	Permission to administer a project in JIRA. This includes the ability to edit project role membership (Enterprise Edition only), 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). Users without this permission will not know that the project exists.
View Version Control	Permission to view the version control information (CVS, Subversion, Perforce etc) for issues. Note that for CVS, to view the Version Control information the project needs to be associated with at least one Repository.
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).
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.
Schedule Issues	Permission to set and edit the 'Due Date' of issues.
Move Issues	Permission to move issues from one project to another, or (in Enterprise Edition only) 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. (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.)
Resolve Issues	Permission to resolve and reopen issues. This also includes the ability to set the 'Fix For version' field for issues.
Close Issues	Permission to close issues. (This permission is useful where, for example, developers resolve issues and testers close them.)
Modify Reporter	Permission to modify the 'Reporter' of an issue. This allows a user to create issues 'on behalf of' someone else.
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 (Enterprise Edition only). Only relevant if issue security has been enabled.
View Voters and Watchers	Permission to view the voter list and watcher list of an issue.
Manage Watcher List	Permission to manage (i.e. view/add/remove users to/from) the watcher list of an issue.
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.
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.
Work On Issues	Permission to log work done 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.)
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.)
Delete All Worklogs	Permission to delete any worklog entries, regardless of who added them. (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

Log in as a user with the 'JIRA Administrators' global permission.
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:
On the panel on the left, under the title "Schemes", 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.

Adding Users, Groups or Roles to a Permission Scheme

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.
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.

(Note: this screenshot is from JIRA Enterprise; in JIRA Professional/Standard only 'Group' and 'Project Role' are available)
Repeat the last 2 steps until all required users/groups/roles have been added to the permissions
To delete a user/group/role from a permission click on the "Delete" link in the "Users / Groups / Roles" column

Associating a Permission Scheme with a Project

Log in as a user with the 'JIRA Administrators' global permission.
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:
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.

Deleting a Permission Scheme

Log in as a user with the 'JIRA Administrators' global permission.
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:
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 the Permission Schemes that are currently defined in your JIRA system. Click on the "Delete" 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 automatically associated with the Default Permission Scheme. (Note that you cannot delete the Default Permission Scheme.)

Note

Copying a Permission Scheme

Log in as a user with the 'JIRA Administrators' global permission.
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:
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/roles assigned to them.