-
Bug
-
Resolution: Fixed
-
Low
-
5.2.7, 5.2.9, 5.2.11, 6.2.3, 6.2.4
-
5.02
-
jira.permission.assignable.group workflow property does not work correctly. Even if a user is not in the specified group to have an issue assignable to him, he can still be assigned although his username does not show up in the Assignee drop-down list.
Steps to reproduce
- Create a new user (test) and add him to jira-developers group
- Copy the default JIRA workflow, add a workflow property to Open step as follows (remember to publish draft):
jira.permission.assignable.group = jira-administrators
- Ensure Project A is using the default Permission Scheme which has Assignable User permission granted to Project Roles(Developers)
- Ensure Project A is using the default Roles, where Project Roles(Developers) contains jira-developers group
- Associate Copy of default JIRA workflow to Project A
- Create a new issue in Project A and try to assign it to the newly created user (test): the user won't appear in drop-down list but if you type the full username (test) and click Assign button, the user can still be assigned
- Remove the jira.permission.assignable.group from the workflow and publish draft. Try to assign again on the same issue: the user now appears in drop-down list as expected
- is duplicated by
-
JRASERVER-38029 jira.permission.assignable.group property not overriding permission scheme
- Closed
-
JRASERVER-38209 jira.permission.assignable.group property doesn't work as expected
- Closed
- is incorporated by
-
JRASERVER-38407 Permissions based on Customfields do not work in all cases
- Closed