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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Security level scheme

There's a group of members in a team in which one member can only view his/her issues while the rest of the members can view all issues including the issues created by that one member who can only view issues that he/she has created. Is this possible?

1 answer

1 accepted

2 votes
Answer accepted
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 25, 2022

Yes, you can do this with an issue security schema.

In the most simple case, define an issue security scheme that has a single level, and apply it to your project(s), then automate or force it so that a security level is always set on the issues in those projects.

Let's say you create an issue security scheme that will offer the users "none" and "restricted".  The "restricted" level should be a rule that says "Group X, and the Reporter of the issue".

When someone sets the level to "restricted" on an issue, then that issue can only be seen by members of group X (i.e. your team) and the person who reported the issue.  Note that the reporter can not be a member of group X.

Also, you will need to put the "security level" on the create (and probably edit) screens, and grant all the project users the right to set the issue security.  But to automate it a bit, you can default the security level to "restricted", and you could also force that in a post-function, listener or automation as the issue is created.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events