How to restrict users to see only issues they created

[Ivan Andrieiev]

Hi everyone, I'm setting up an Issue Security Scheme on a company-managed Jira Cloud project (Standard plan) to restrict two users so they can only see issues where they are the Reporter. I've created a security level with Reporter only — which means each user sees only their own issues, but they cannot see each other's issues. However, in my case both users should see each other's issues too, and if I add them as a Project Role to the security level, they see ALL issues in the project which is not acceptable. What is the correct way to allow a group of users to see only issues created within their group, without exposing the rest of the project issues to them?

[Aaron Pavez _ServiceRocket_]

Hi @Ivan Andrieiev 

>  I've created a security level with Reporter only — which means each user sees only their own issues, but they cannot see each other's issues.

This is correct. They wont be able to see the other person work item since the reporter only allows one user. so user A will see only his work item not user b, although both are reporters. not not reporters of both work items.

You will have to use a group for this. Assign the security level to the group and all of those in the group will be able to see those work items. wither group custom field or group.

> What is the correct way to allow a group of users to see only issues created within their group, without exposing the rest of the project issues to them?

Another security level for assignee for example. if im assigned to a ticket, i can see it.

or a mix of reporter and assignee. then the other security level for the group.

A quick video explaining security levels

https://www.youtube.com/watch?v=qbS5COrug0E

Regards

[Trudy Claspill]

Hello @Ivan Andrieiev 

Welcome to the Atlassian community.

Just to make sure I have correctly understood your scenario I'm going to try to parrot it back to you.

You have users A, B, C, D, E, and F

Users A, B, C, and D should be able to see all issues regardless of who the reporter is.

Users E and F should see only issues where E or F is the reporter.

Is that correct?

[Trudy Claspill]

@Ivan Andrieiev 

Assuming the above is correct:

Security levels define who can see the issue, not who can't see the issue. The users who can't see the issues are implied because they are not among the ones who are included in the Security Level.

Therefore you need to get all the users who have the Browse Projects permission, excluding E and F, into a group or project role or multiple groups/project roles as long as E and F are not in any of those groups/roles.

Then in your security scheme you would make a level that allows only visibility only for members of those groups/roles.

You would set None as the Default Security Level in that Security Scheme.

As issues are created they initially would have no security level and be visible to everybody with Browse permission in the project.

You would also create an Automation rule for that project that is triggered by issue creation.

You would follow that with a condition like this to check if the Reporter is not one of the users who should be limited in the issues they can see.

 

If this condition is met, the restricted users are not the Reporter of this issue and they should not be able to see it.

The next step is to set the issue Security Level for the issue.

 

You would select the Security Scheme and Level you created earlier.

That sets this issue to be visible to everybody except the restricted users when the Reporter is not one of the restricted users.

Ir the Reporter IS one of the restricted users, then the security level remains set to None and all users with Browse Projects permission can see it, which includes the two restricted users.