Join Sandra Toner for an in-depth discussion in this video Setting security controls for an issue, part of Atlassian JIRA: Installing and Administering.
- In this video, we'll set security controls on an issue. Setting the security level on an issue restricts the access of that issue only to people who are a member of the chosen security level. If you're not a member of that security level, you won't be able to access the issue, and it won't appear in filters or queries. To associate an issue's security level with a project, you'll need to add it to the issue's security scheme. Once the issue's security scheme has been updated, the security levels can be applied to issues in that project.
First, we'll go into system administration, and configure security levels. Keep in mind that you have to have the JIRA administrators global permission to do this. Let's get started by adding a security scheme. To do this, go to the administrative menu and select Issues. Now, you'll scroll down and select Issue Security Schemes. You can see on this page, I already have two security schemes created. Let's go ahead and create a new security scheme. Click on the Add Security Scheme button.
Now you'll name your security scheme, and click the Add button. Now you can see that the security scheme has been added to the list. Now it's time to add a security level to our issue security scheme. In the same row with the issue security scheme that you're interested in, under the Operations column, click on Security Levels. Our new issue security scheme currently doesn't have any level. Select Add Security Level, and type in a name. Let's go ahead and add another security level.
Once you've added your security levels to your issue security scheme, you'll also need to add users, groups, or project roles. To do this, click on the Add link under the Operations column. Here you can select a group or a user to add to this security level. I'll go ahead and add the entire JIRA administrators group. For low security, I'll select the Reporter. This means that whoever is the Reporter on the issue can select the issue security level.
Now that we've set up a new issue security scheme, and added two different security levels, let's go back and associate this scheme with our project. First, let's open up a project. I'll select Project from the header menu, and choose the Software Development project. Now, in the Administration panel on the left, I need to select Issue Security. Here you can see that the current issue security scheme is set to 12345. Let's go ahead and change that to the security scheme that we just created.
Click on the Actions button, and select Use different scheme. Now, from the dropdown, you should be able to select Security for HQ Issues. The security scheme we just created. If there aren't any previously secured issues, or if the project didn't previously have an issue security scheme, you can skip this next step. If there are previously secured issues, which we can tell there are because it shows the security level of executive level and three affected issues, we'll need to select a new security level to replace the old level.
All issues with a security level from the old scheme will now have a security level from the new scheme. You can choose None if you want the security to be removed from all the issues. So far, we've created a new issue security scheme and added security levels. We then associated that scheme with our project. Let's create a new issue, and look for the security level field. You can see the third field down is the security level. Because I'm part of the JIRA administrators group, I have access to select High Security, and because I happen to be the reporter on this issue, I can also select Low Security.
As you can see in the view issue screen, the security level shows up under the Details heading. If you want to change the security level from the view issue screen, hover over the security setting, and select another setting. Make sure that you click on the check mark to save your change. Remember that you'll only be able to see the security levels that you belong to. I just set this issue to a security level of high security. That means that only users in the JIRA administrators group will now be able to see this issue.
In the next video, we'll work on cloning, linking, and moving an issue.
- What is JIRA?
- Installing and configuring JIRA
- Reviewing reports and issues
- Understanding the JIRA workflow
- Managing roles and users
- Cloning, linking, and moving issues
- Searching JIRA
- Personalizing the dashboard and user profiles
- Generating reports
- Customizing the workflow
- Using JIRA add-ons
- Making JIRA agile