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

Skip to end of metadata
Go to start of metadata

This tutorial provides a step-by-step guide for creating project roles and using them in an issue security scheme. We recommend creating a test project and two test users for this tutorial.

Tutorial Goal

Icon

When completed, this tutorial will provide two issue security levels. One for issues that specific customers and your company can view, another for internal company eyes only.

1.Adding Project Roles

First we need to create project roles for our scheme to use:

Administration -> Users, Groups and Roles -> Project Role Browser -> Add Project Role

  1. Create a project role called Customer A.
  2. Create a project role called Customer B.
  3. Create a project role called My Company.

In this example, the My Company project role will always have the same users/groups for each project. As a result, we'll set default members that will be used for all projects that use this scheme.

  1. Next to the My Company project role, click Manage Default Members.
  2. Add the users or groups for your company by clicking Edit next to the appropriate default (users or groups).

2. Adding an Issue Security Scheme

Next, we need to create the issue security scheme which will be hooked to our test project a bit later in this tutorial:

Administration -> Schemes -> Issue Security Schemes -> Add Issue Security Scheme

  1. Add a new issue security scheme called Customers and My Company Issue Security Scheme.

3. Adding Issue Security Levels

We need to add security levels for this new issue security scheme. These levels will be available for selection to those that have permission to add issue security levels to issues. Users can only see levels of which they are members.

Administration -> Schemes -> Issue Security Schemes -> Click the Security Levels link next to Customers and My Company Issue Security Scheme

First we need to add a level for each customer:

  1. Add a new issue security level called Customers and My Company.
  2. Add the Customer A, Customer B and My Company project roles to this issue security level.
  3. Click Default to make this the Default.

Next, we want a level for internal company eyes only:

  1. Add another issue security level called My Company
  2. Add the My Company project role to this issue security level.

4. Associating your Issue Security Scheme with a Project

Explain the step here and use the following syntax and color for menu notations:

Administration -> Project -> Projects -> Click on your test project name

  1. For the Issue Security Scheme option, click Select.
  2. Choose the Customers and My Company Issue Security Scheme from the list.
  3. Click Next.
  4. If you would like to associate existing issues with a security level, select it from the list, if not leave it at None.
  5. Click Associate.

5. Adding project-specific members to a project role.

We need to specify the project-specific role members for the Customer A & B project roles.

Administration -> Project -> Projects -> Project Team -> Project Roles -> View Members

  1. Add the first test user to the Customer A project role by clicking Edit in the Users column.
  2. Add the second test user to the Customer B project role by clicking Edit in the Users column.

Project roles allow you to use the same permission scheme for multiple projects. We can change the members of project roles via the project!

Did it work?

Icon
  1. Create one issue and set the Issue Security Level to My Company.
  2. Create another issue and set the Issue Security Level to Customer A.
  3. Create one more issue and set the Issue Security Level to Customer B.
  4. Try logging in as each test user to ensure that they only see the appropriate issue.