I have a user X that according to the permission scheme is allowed to be assigned to an issue. The issue is tied to a security scheme, where the Role the user belongs to, is not allowed to see the issue BUT the role "current assignee" is. (set up this way, because I only want the user X to see the issue, if user X is assigned to the issue). However I can't assign user X, because of this security level. Is the any smart work around for this?
https://jira.atlassian.com/browse/JRA-38134 sort of touches on the same issue, but from the opposite angle, and I don't think they had "Current assignee" as a part of their Issue Security Scheme.
No, this is a known problem - you can't assign issues to people who can't see them yet. So they need to be able to see the issue before they become the current assignee.
In other words, using "current assignee" in security schemes is pretty much useless, and you can't do "user can only see issues assigned to them"
Well, the trick I've used is to create a new user-picker field that is not limited like assignee. Then when the transition or edit is committed, a script takes the user selected in there and tries to apply it to the assignee field. The weakness is that a user-picker lists everyone, not just the possible assignees.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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