This is to limit the visibility on an issue. You set the security level when you create/edit an issue.
You cannot override the project permissions though. That means you will have to open the project to all (say X & Y) and then limit the issue to selected users (only X or Y)
Think of it in layers. The first is the "permission scheme", which is at project level. If that blocks them from the project, then that's it, they see nothing more. Issue security is irrelevant because they can't get past the first layer. Then, there's a second layer, of "issue level security" which is based on an attribute on the issues. That's checked for each issue they might try to look at in the project to see if they are allowed to.
You set project security at the project level as a one-off. Issue level security is done by a field on each issue which you can have on the issue create screens.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
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