Issue visibility by group of assignee

I need the following:

When i assign a user to an issue, the issue must be visible to the user and the group and Project Role where the user is.

I will make an example to illustrate:

  • Bob, Mary and Ana are in the group A. 
  • July and Oscar are in group B. 
  • Bob, Ana and July are in the Project role of "Devs"
  • Mary and Oscar are in the Project Role of "Readers"
  • When someone assign Bob to an issue
    • The issue must be visible to Bob and Ana (Cause they are in the same group and project role)
    • The issue must not be visible to Mary, Oscar and July
  • But if we change the asignee to Oscar
    • The Issue must be only visible to Oscar

So a Issue only have to be visible to the user assignee and Intersection of group and project role the user belongs.

Do you know how to do it?

2 answers


You may check "Issue security schemes" in Administration > Issue.

You can create security level based on groups/project role/...

In the screen of the issue, insert the field "level" and fill it with a security group.

Only the users in the right security group will be able to see this issue.


Yes, that way is the way i know, but the case i have is different, i dont know the group to restrict the issue security scheme. JIRA may read the group and Project role from the asignee and only let see the issue to the users in the intersection of Project role and Group from asignee.

No, JIRA does not read anything from  the assignee.  The assignee is the assignee.

I know, what i am asking, if there is a way to do it

Mmmm the way i see it, your main question is "is there a way to create groups that automatically add user in terms of their groups ?"

Actually, issue security schemes can be set through field. Maybe you can use that.

But the problem may remains the same since the main difficulty is that you don't know the people to put in the security level in advance.

Maybe there are solutions in the JIRA API that can help you through programmation.



0 votes

You can't do this.  The fact that the issue is assigned to Bob has nothing to do with the visibility of the issue except for when you want to implement a rule for "assignee can see the issue".  Bob's groups and roles may also let him see the issue, but they have nothing to say about who else can see the issue.

You need to set up a security scheme that allows you the right visibility rules, and then set the right security level for the issue at the same time you are assigning it.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,294 views 5 10
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you