Issues are not shown by Issue Navigator when reporter performs a search when Issue Security Level is activated and reporter account comes from an external user directory


We are intending to use JIRA as a Support System but we just found a problem concerning Issue Security Level and Issue Navigator that we think it could be a bug.

We followed the instructions provided by Atlassian in order to configure Project Security and Issue Level Security. We created a permission scheme with one security level (activated by default) and added the Reporter issue role and an internal group as the only role/groups having permissions to see the issues. Additionally, we added the Browse Projects permission to that group and Reporter role too.

All of that works like a charm when we talk about users belonging to JIRA Local Directory. However, we use and external user directory (Microsoft Active Directory is our corporate user repository). When an user whose account is in this external directory creates an issue, he can browse the issue directly but he can’t see it in the Issue Navigator instead. I mean, the issue is not shown in the Issue Navigator when user performs a search, but instead he can see the issue key in the dropdown Issues menu (Recent issues) and he can browse it. How is it possible?

As I already said, all of that works fine when reporter account is in the JIRA Internal Directory.

So, in brief, it seems there is an abnormal behaviour when Issue Security Level is applied and a user whose account is in an external user repository tries to see, through the Issue Navigator, the issues reported by himself.

That problem is critical for us as long as it prevents we can use JIRA as our corporate Support System.

Thanks in advance for your help.


2 answers

1 accepted

1 vote
Accepted answer

This is problem is solved by following JRA-27590

2 votes
Ruchi Tandon Atlassian Team Feb 06, 2013

These type of ptoblems are generally result of corrupt indexes.

Have you tried indexing the instance? Does it help?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

36 views 1 5
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