The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do I restrict issues for a group based on a custom field on an issue?

newuser9876
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 14, 2023

Hi,

In my project (I am the Cloud Admin) I have created a custom dropdown field on our issues called "Workstream".

How can I configure Jira to only allow a certain group of users see issues when the workstream dropdown selected is set to "Business"? They shouldn't have access to any other issues.

I have created the group and the Security Scheme and the Level but I'm just not sure how I create the condition / permission to say deny access to all issues unless workstream = business.

Thanks so much in advance!

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Trudy P Claspill
Community Champion
December 14, 2023

Hello @newuser9876 

Welcome to the Atlassian community.

To deny visibility to an issue with Security Levels you have to assign a Security Level to the issues you want to hide. The Security Level has to be configured in a way that the users you want to hide the issue from are not included in the Security Level.

Then you need to have a second Security Level that includes all the users of the first Security Level, plus the users who should see the "Business" issues. 

You would initially assign the first Security Level to all issues, hiding all issues from the specified group. Then you would use Automation to change the Security Level to the second Security Level if the Workstream field was changed to "Business". You would also want the Automation to change the Security Level back to the first one if the Workstream issue was changed again to something other than "Business".

To ensure that all happened automatically, you would probably want to restrict the Set Security Level permission so that end users in both Security Levels would not be able to manually set the level to make the issue visible to the restricted group. You might want to give that permission only to Administrators.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events