Vote #76270
完了Field permissions not working properly with inherited memberships
0%
説明
I have a tree of projects, were groups and permissions are assigned in the top of the tree and projects inherit members.
I have several fields (custom and non-custom) which are not required, but required in several Status.
I haven't figured how to 100% reproduce it, but when assigning a user in several groups, and those groups different roles (ex. group developers, groups project managers, with role developer and project manager), the required fields depending on the status are no longer REQUIRED.
Configuration of the fields permission workflow is exactly the same in the role developer and project manager. On the Fields permissions Workflow I can see the "Required" keyword on the fields when filtering by role "all".
This issue is quite important as we depend on giving permissions to that structure.
journals
I checked that a same user has assigned the same role by directly assigning the role in the group, and also because he is inheriting it, this issue is happening.
I looks like this is the cause, and not that the user is in multiple groups.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Fixed in r14179. Thanks for pointing this out.
--------------------------------------------------------------------------------
Thanks for the fix!
Expecting version 3.0.2 :)
I hope this issue fixes all the possible variations that cause the fix!
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
related_issues
duplicates,Closed,25258,Field permissions ignored if the user and the group one belongs to share the same role