Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Issue secuirty levels

Mane Zakaryan
Contributor
May 16, 2022

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 Funk
Community Champion
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. 

Mane Zakaryan
Contributor
May 17, 2022

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 Funk likes this
John Funk
Community Champion
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