How can I restrict access to the reporter and specific groups based on custom issue value?

[Haris Psarropoulos]

Hello all,

I am facing troubles applying security on a specific Service Desk project we have in our company. What we want to achieve, is for two groups of people to work on their tickets without having access to the tickets of the other group based on a one of the custom fields we have in the ticket. So if the custom field has value A, only the reporter and people from group A should have access to the ticket, similar when the custom field has value B, only the report and people from group B should have access to the ticket.

I have checked the below resources:

https://confluence.atlassian.com/jirakb/automatically-set-work-item-security-level-based-on-jira-group-membership-726565612.html

https://support.atlassian.com/jira/kb/restrict-access-to-certain-jira-issues-based-on-the-value-of-a-custom-field/

and have created a Security Scheme with two Security Levels, each assigned to a specific user group. I have started working on the automation rule, but whenever I reach the step to edit the work item and set a security level, I only get the options:

• Internal
• Reporter Only

I tried with both having Work Item Security set to None and set to my newly created Security Scheme.

What am I missing? Is there a way to achieve this kind of automation?

Thank you

[Marc - Devoteam]

Hi @Haris Psarropoulos 

Can you show your Security Scheme setup and the following automation rule details:

1. what type of project is this (e.g., company-managed, team-managed, etc.), 

2. images that show your complete rule.

3. images showing the details of any relevant actions/conditions/branches.

4. images showing the Audit Log details for the rule execution.

5. Explain where the issue is.

Or see this KB article automation-or-set-issue-security-level-via-automation-for-jira 

[Haris Psarropoulos]

This is my rule:

The project is a Service Desk Project (company managed as far as I remember).

This is my security scheme with the security levels:

The main problem I have is when I try to create the rule, as you can see in the first pic, when trying to select Security Level, I get only those two options, I was expecting to see the security levels I had created in order to select one of the two and then create a second rule for the other security level.

[Marc - Devoteam]

Hi @Haris Psarropoulos 

Is this security scheme associated to the project.

Based on the options shown in the automation and the scheme itself not. It seems another security scheme is used on the project.

[Haris Psarropoulos]

According to the instructions on the resources I attached in the original question the project should be connected to None security level. But I have tried both having none and the shown security level. In both cases, I only see Internal and Reporter Only options in the rule action.

[Marc - Devoteam]

Hi @Haris Psarropoulos 

You created a security scheme right?

Did you associate this scheme to the project, I suspect not.

Security Schemes can only be used on Company Managed projects, so if your project is a Team Managed project, this can't be done.

Please provide some screenshots of your configurations in the project.

[Haris Psarropoulos]

As far as I can see, the project is company managed. I just connected the security scheme to the project:

And still, when I try to configure the rule, I see the same options:

What other screenshot would it help you?