- Set up a JIRA site
- Add users
- Create a project
- Create an issue
- Search for issues and create reports
- Configure permissions
- Configure workflows and screens
- Extend JIRA
You won't want every user in your team to have the same level of access to JIRA. For example, you may want to restrict who can administer JIRA, or prevent users from viewing a project. In this stage, you will learn about the different permissions in JIRA and try setting permissions for a project.
Before we start, it is important to understand how JIRA permissions work. There are two levels of permissions in JIRA: global permissions and project permissions.
Global permissions cover a small set of functions that affect all projects in JIRA. For example, permission to administer JIRA. They can only be assigned to groups.
Project permissions cover a set of more granular functions that affect a single project in JIRA. For example, permission to create issues in a project. They can be assigned to groups, users and roles.
About Roles, Groups and Users
A role is a project-specific set of groups and/or individual users. Roles are a way of abstracting users/groups from project permissions.
For example, in your team, you may have 'scrum masters' who are responsible for assigning issues in projects. Your product managers (PM) are 'scrum masters' on every project, but individual developers may also be 'scrum masters' on specific projects.
In JIRA, you can define a 'scrum master' role that includes the PM team on all new projects. You can then define a set of permissions that grant the 'assign issue' permission to this role, and apply this set of permissions to all projects. Individual developers can be added to the 'scrum master' role on each project, as needed.
This is much easier to manage than defining different sets of permissions for each project.
Let's try it out! In the following steps, you will use project permissions to hide a new project from some of your users.
Step 1. Create a new project role
This project role will only contain users that you want to view a particular project. We will assign permissions to this role in the next step.
- Navigate to the 'Project Role Browser' screen using the quick operation: . + roles.
- Add a new project role: Big Kids.
- Add yourself and Alana to the Managers project role via Manage Default Members > Edit (under Default Users). Do not add William.
Step 2. Configure a new permission scheme
The 'Browse Projects' permission controls whether a user can browse a project, i.e. whether they can view the project. You will assign this permission to your new role.
- Navigate to the 'Permission Schemes' screen using the quick operation: . + permission schemes.
- Copy the Default Permission Scheme, then edit the copied scheme and change the name to Confidential Permission Scheme.
- Click Permissions for Confidential Permission Scheme. For the Browse Projects permission:
- Choose Delete for 'Project Role (Users)'.
- Choose Add, select Big Kids in the Project Role field and save.
Step 3. Associate the scheme with a project
- Choose Project > Create Project and choose the Project Management project.
- Name the project Top Secret Project and Submit.
- Choose Administration (tab) > Permissions (left menu) > Actions > Use a different scheme.
- Set the Scheme to Confidential Permission Scheme and Associate.
The only users that can browse your new project are Alana and yourself (note, default members are only added to a role for new projects). Try browsing the project with William. You could also use this approach to restrict users from creating issues, adding comments, closing issues, etc, in a project.
Congratulations! You configured project permissions to hide a project from users.
Next you will learn how to edit workflows and screens in JIRA.