Jasen, I understand your comment. As Jobin pointed out, two different permission settings govern the ability to view issues or be assigned issues within a project. JIRA constantly checks permissions and the issue level security is doing it's job by preventing visibility. There is no built-in linkage between those two permission configurations. More on Issue Level Security -
If you're looking to sync things up, considering leveraging project roles in both your issue security levels and your permission scheme to prevent such disconnects. It may take a bit of planning, but I'm sure you can accomplish your goals.
I swear at one time people that were not in a security level wouldn't be able to be assigned to an issue. This just sounds like a bug. We have pretty extensive security levels where I work and now I could have issue assigned to me and not even know it because the security level isn't set correctly. Doesn't sound like a good thing.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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