Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

How do I hide issues which are not in my security level in issues navigator

Edited
Subodh Sohoni
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!
Nov 08, 2023

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?

2 answers

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 08, 2023

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)

  • None: Everyone can see the issue
  • Green: Team 1 and Team 2 can see the issue
  • Blue: Team 1 can see the issue

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)

0 votes
Subodh Sohoni
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!
Nov 08, 2023

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events