Ability to secure issues within a project by field value?

[Mercker, Jeramie]

Greetings!  

Here's the problem I'm trying to solve:

I need to limit the issues that a user can see within a given project by a field value on the issue.  As an example, I might have a custom field "State" that has a value indicating the US state that the issue is about.   I'd like to be able to setup a security rule where a user has read only access to issues with a State field of "GA" but cannot see any other issues within the project.

Is this possible in JIRA?  If so, how?

Thanks!
Jeramie

[Stefan Salzl · Accepted solution]

Hi @Mercker, Jeramie - welcome to the community,

yes, this is possible. The feature of your choice is called „issue security level“.

You can create a security level scheme and define different security levels that control/limit who can see issues. 

See the description here:

https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Furthermore this would need an automation rule to set/change the security level of an issue regarding to your requirement/custom field value.

Hope I could give some helpful hints.

Best
Stefan

[Mercker, Jeramie]

Thanks a LOT for the quick reply and the detailed response.  I appreciate it!  I'll check the docs and see what we can do.

[Mercker, Jeramie]

@Stefan Salzl - Do you have any reference material / docs on the automation part of it?

Thanks!

Jeramie 

[Mercker, Jeramie]

@Stefan Salzl this is what I need on automation right?  https://support.atlassian.com/cloud-automation/docs/create-and-edit-jira-automation-rules/

[Stefan Salzl]

Hi @Mercker, Jeramie 

yep, this is quite a good point to start. Furthermore I recommend to check out the „basics“ here:

https://www.atlassian.com/software/jira/guides/automation/overview

This will also guide you to the different components of automation like triggers, conditions and actions.

As far as I got your requirement I guess it would be starting with a field value change trigger when your required field changes then working with „if-condition“ blocks to set a special security level according to your special value in that field. (in case you have a list of valid valid that could go to this field and those values are kinda mapped to special security level I would recommend to create that field as a select field to avoid wrong field inputs that would break the automation rule).

Don‘t hesitate to get back and ask in case you get stuck while creating that use case ;)

Best
Stefan

[Mercker, Jeramie]

Thanks @Stefan Salzl !  This is a great community.  I hope I can start giving back in the near future.

[Mikael Sandberg]

Hi @Mercker, Jeramie,

Welcome to Atlassian Community!

Yes that is possible and you can do it using issue security and automation. Have a look at this KB for more information on how to set it up. Basically you create an issue security scheme and once added to the project you can create an automation that monitors your "State" field to set the right security level on the issue.

[Mercker, Jeramie]

Thanks Mikael!  I appreciate the quick reply and this information.  It looks like between your reply and Stefan's this is the way to go.  I'll have to get this checked out.

[Trudy Claspill]

Hello @Mercker, Jeramie 

Welcome to the Atlassian community.

Are the issues in a Company Managed project or a Team Managed project?

@Stefan Salzl 's answer applies if the issues are in a Company Managed project.

[Mercker, Jeramie]

Thanks for the quick reply!  These are all Company Managed projects.  I'll check Stefan's reply.