We have a Jira project in which one team (Team 1) works on many tech projects. Another team (Team 2) works on only Mobile Application. We wanted to have users in Team 2 to have access to 'only those issues' that are for Mobile App.
We created 2 separate groups. Team 1 and Team 2.
We also created a security level named Team 2. We added Team 2 and Team 1 in this SL. We did not add Team 2 in other SLs but added Team 1 only. These security levels are based upon value of a custom field. If the value of that is Mobile App then an automation rule sets the SL to Team 2, for other values some other SL is set.
In Backlog and Current Sprint users of Sprint 2 can view only those issues that are for Mobile App.
In issue navigator, (Issues attribute), users of Team 2 can view all issues.
How can I prevent users of Team 2 from accessing issues other than for Mobile App even in the issue navigator?
Welcome to the Atlassian Community!
I am not too clear on what you have set up, or where the problem is.
At the moment, your available security levels (I've changed the names to avoid confusing Team 2 with Team 2)
Is the problem that Team 2 can see issues with the security level set to "Blue"?
(Forget the boards for now, they have more complexity to look into, and are not the underlying problem)
All those issues that were shown in the Issues attribute for the user from Team 2 were such issues which did not have any SL. These were quite a lot.
This behavior is not to my expectation. I expected that if the user is in a group that is only in a specific SL then even the Issues attribute should show issues only from that SL and not even the issues which do not have any SL.
I find this as a bug and would like to report it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.