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 Issue security Why use issue security? Creating an Issue Securit.. Setting the Default Secur.. Adding a Security Level t.. Adding Users/Groups/Proje.. Assigning an Issue Securi.. Deleting an Issue Securit.. Copying an 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

Issue security

PDF

Issue security levels are a JIRA Enterprise feature that allows you to control who can see individual issues within a project (subject to the project's permissions).

An issue security level is a named collection of users. Issue security levels are created within issue security schemes, which are then associated with projects. Once an issue security scheme has been associated with a project, its security levels can be applied to issues in that project. Those issues will then only be accessible to members of that security level.

A security level's members may consist of:

Individual users
Groups
Project roles
Issue roles such as 'Reporter', 'Project Lead', and 'Current Assignee'
'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.

Note

Only users with the project-specific 'Set Issue Security' permission can apply a security level to an issue, regardless of whether they are members of the security level.

Please note that issue security levels are only available in the Enterprise edition of JIRA.

Why use issue security?

As an example, a company may have a public instance of JIRA running. Within this instance they may have several projects that external people (customers) can browse. However, it may not be appropriate to show all issues to the customers. To achieve this you could:

Create an issue security scheme.
Create an issue security level named 'Private' for this scheme.
Add appropriate people to the 'Private' security level.
Associate the issue security scheme with the relevant projects.
Set the security level of specific issues to 'Private'.

Creating an Issue Security 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 the link labelled 'Issue Security Schemes'.
This will display the 'Issue Security Schemes' page. This page lists all of the Issue Security Schemes that JIRA currently has. Click the 'Add Issue Security Scheme' link.
In the 'Add Issue Security Scheme' form, enter a name for the issue security scheme, and a short description of the scheme. Then click the 'Add' button.
You will return to the 'Issue Security Schemes' page, which now contains the newly added scheme.

Setting the Default Security Level for an Issue Security Scheme

You can choose to specify a Default Security Level for your issue security scheme.

The Default Security Level is used when issues are created. If the reporter of an issue does not have the permission 'Set Issue Security', then the issue's security level will be set to the Default Security Level. If the project's issue security scheme does not have a Default Security Level, then the issue's security level will be set to 'None'. (A security level of 'None' means that anybody can see the issue.)

To set the Default Security Level for an issue security scheme, go to the "Edit Issue Security Levels" page, locate the appropriate Security Level and click its 'Default' link.
To remove the Default Security Level for an issue security scheme, go to the "Edit Issue Security Levels" page and click the 'Change default security level to "None"' link.

Adding a Security Level to an Issue Security 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 'Issue Security Schemes'.
This will display the 'Issue Security Schemes' page. This page lists all of the Issue Security Schemes that JIRA currently has.
Click on the name of any scheme or the link 'Security Levels' to bring up the 'Edit Issue Security Levels' page.
In the "Add Security Level" box, enter a name and description for your new security level. Then click the button 'Add Security Level'.

Adding Users/Groups/Project Roles to a Security Level

Go to the 'Edit Issue Security Levels' page (see above).
Locate the appropriate Security Level and click its 'Add' link:
This will display the "Add Issue Security" page. Select the appropriate user, group or project role, then click the "Add" button.
Repeat steps 2 and 3 until all appropriate users and/or groups and/or project roles have been added to the security level.

Assigning an Issue Security Scheme to 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 the 'Select' link beside the 'Issue Security Scheme' caption.
This will bring up a list of Issue Security Schemes. Select the Issue Security Scheme that you want to associate with this project.
If if there are no previously secured issues (or if the project didn't previously have an issue security scheme), skip the next step.
If there are any previously secured issues, select a new security level to replace each old level. All issues with the security level from the old scheme will now have the security level from the new scheme. You can choose 'None' if you want the security to be removed from all previously secured issues.
Click the 'Associate' button to associate the project with the issue security scheme.

Deleting an Issue Security 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 'Issue Security Schemes'.
This will display the 'Issue Security Schemes' page. This page lists all of the Issue Security Schemes that JIRA currently has. Click the 'Delete' link for the scheme that you want to delete.

Note

You cannot delete a Issue Security Scheme if it is associated with a project; you must first unassign the scheme. To unassign a scheme, please refer to Assigning an Issue Security Scheme.
A confirmation screen will appear. To delete, click 'Delete'; otherwise click 'Cancel'.

Copying an Issue Security 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 'Issue Security Schemes'.
This will display the 'Issue Security Schemes' page. This page lists all of the Issue Security Schemes that JIRA currently has. Click the 'Copy' link for the scheme that you want to copy.
A new scheme will be created with the same security levels and the same users/groups/project roles assigned to them.