nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do you restrict a user from a specific issue type?

Jonathan Whitford

I'm using JSM cloud for HR service management and would like to restrict access to a particular issue type because only a specific list of users needs access to view and edit those service requests.

What is the best way to configure access permissions so that only specific members of my team can see this issue type?

For reference:

Project = Human Resources

Group with access = HR team (all team members have access)

Issue type to restrict = leave requests

Appreciate any suggestions!

Accepted answers

Mikael Sandberg

Hi @Jonathan Whitford,

Welcome to Atlassian Community!

You can achieve this by using issue security. Then on the Leave requests you can set the security to only allow for example the HR team and the reporter to see the request. Have a look at Configure issue security schemes for more information on issue security.

All comments

Mikael Sandberg

Hi @Jonathan Whitford,

Welcome to Atlassian Community!

Jonathan Whitford

Thank you, @Mikael Sandberg I have read through the link and it's helpful.

One step I seem to be missing is how to associate the issue security scheme with a specific issue type. I am able to apply it to a project under Project Settings, but cannot figure out how to apply it to just one issue.

In this case, I am looking to configure so that everyone on my team has access to view and edit all issues in our project EXCEPT one that only a subset of my team requires access to.

Mikael Sandberg

What controls the access is the Security Level field. If all your issues are following the same workflow you can either use automation to set the field based on the request type, or manually set it by adding the Security Level field to the screen and change it. If the issue that you want to limit access to is using a different workflow you can set the security level as a post function on create.

Mikael Sandberg

Here is an example of a security scheme I created for a HR demo project

Screen Shot 2021-04-21 at 1.52.40 PM.png

Onboarding is open for everyone, and if I change it to HR the issue will only be visible for the requestor and the HR team.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management