Community moderators have prevented the ability to post new answers.
I think your problem and solution is the same as that of allowing customers to create issues but not view them, described here: http://confluence.atlassian.com/display/JIRA/Letting+customers+only+create+issues
IE, the permission violation happens, but the users are redirected to a nicer page so they don't think the operation failed.
So your assignee changes on the transition, right?
Issue Security Schemes allow for different things, including a user picker or group picker custom field. One solution would be to add yourself to a user picker custom field, then add that custom field to the security scheme. Have users add themselves to that custom field each time. Depending on what you want to do, you might be able to put everyone in a project role, then add that project role to the issue security scheme.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Issue Security Schemes is working perfectly.
The problem is that the "Issue Security Levels" I added "Current Assignee".
For example, the issue is with this "user1" shortly after he make the transition to "user2" appears the message "permission violation" because he is no longer the "Current Assignee". The transition is successful, but because of the message "permission violation" the User thinks is a mistake and that the transition was not completed.
What better way to solve?
Thanks a lot!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.