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

Issue secuirty levels

Hi everyone.

I need your help.


In my Jira project I have permission's groups and Projects.  For example I have
Permission group ''Group X PM''
Permission group ''Group X''

And I have a project X


When I create the issus in the project X and I assign the issues to people who are in ''Group X PM'' or ''Group X'' (also they have acces to the project X), I need make so that people in the group permission ''Group X PM'' can see all created issues in the project.

At the same time, I want that people in the ''Group X'' see only the issues that are assigned to them.


How to do this ?

I already created the Issue security scheme and in this scheme I created some levels and in the levels I added the ''Group X PM'' and ''Group X'' it that security level.


Then, I associated the Issue Security scheme to my project X.


Then, in the permission schemes I have ''Set Issue Security'', but I don't understand how manage it so I have what I want.

1. People in ''Group X PM'' see all the issues, no matter who is the asseignee

2. People in ''Group X'' see only their own issues







1 answer

1 accepted

0 votes
Answer accepted
John M Funk Community Leader May 16, 2022

Hi Mane,

Can you share screen shots of what you have so far? 

Basically, you need a level for Group X PM that includes that group but not Group X.

Then you need a second level for Group X which includes BOTH groups. 

When you assign a level to an issue, Group X PM people will see all issues regardless of which level you use. 

But you should assign Group X level to those issues that you want the Group X people to see. Otherwise, assign the Group X PM level to issue which will hide it from Group X people. 

Thank you for reacting to my post.

Finally I found what I wanted.

In fact, I have created a ''ISSU SECURITY SCHEMES'' and I have created ''SECURITY LEVELS'' for each schemes.

I also did the association with my project and I have done the configuration in the permitions for the field '' SET ISSUE SECURITY'' for my project.

But I didn't understand that I should also add a field ''SECURITY LEVEL'' in the Issue when I am creating it.

So when I configured also the field ''SECURITY LEVEL'' with its default value, then when I create new issues in my project they already have this field and it is managed by the permissions that I set up. So now I can control who can see the issue and who can not.


For existing issues I selected all of them user by user in Kanban and I did ''BULK CHANGE'' for adding this missing security level isntantly for all of them as I had more than 1000 issues for the project. So here the ''BULK CHANGE'' was really helpful.

Like John M Funk likes this
John M Funk Community Leader May 17, 2022

Great! Glad this is working well for you!

Like Mane Zakaryan likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,571 views 37 45
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you