-
Bug
-
Resolution: Fixed
-
Medium
-
6.3.6
-
6.03
-
For JIRA versions before JIRA 6.3.6, it used to be possible to assign issues to a user, even though the user didn't initially have the security level permissions to see the issue.
- The advantage of this previous configuration is that if you have 'Current Assignee' added to your security level, the user automatically is able to get access to the issue as soon as he is assigned.
However, in JIRA 6.3.6 this is no longer possible.
Steps to reproduce
- Set up issue security scheme for your project.
- Create an issue and restrict it to a specific security level.
- Try to assign this issue to a user who originally didn't belong to the security level.
Expected Behaviour
- JIRA allows you to assign the issue (as in JIRA versions before 6.3.6)
Actual Behaviour in JIRA 6.3.6
- You get an error "User 'xxx' cannot be assigned issues."
- is caused by
-
JRASERVER-38407 Permissions based on Customfields do not work in all cases
- Closed
- is duplicated by
-
JRACLOUD-66060 Assignable Users are not assignable for an issue if they don't belong to the Issue Security Level permissions
- Closed
-
JRASERVER-40142 JIRA quick edit Assignee fails with wrong message: User ... cannot be assigned issues
- Closed
- is related to
-
JRASERVER-38134 Warn when/prevent from, assigning issue to user who does not have appropriate security level
- Gathering Interest
- mentioned in
-
Page Loading...