Why can an issue be assigned to someone when the issue security level forbids them from seeing it?

[Charles Wells]

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 - 

https://confluence.atlassian.com/display/JIRA/Configuring+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. 

[Jasen Sparacino]

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.

[Jobin Kuruvilla [Adaptavist]]

It is just two different permissions, that's all. You have to make sure they can see the issue before assigning it to them or remove those users from the "Assignable Users" permission.

[Jasen Sparacino]

I would think that JIRA would be smart enough to not allow you to assign an issue to some that can't access it.

[Jasen Sparacino]

This also stops them from getting email alerts that they have been assigned and issue as well