Project

General

Profile

Actions

Defect #19569

closed

Field permissions not working properly with inherited memberships

Added by Ricard F over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Urgent
Category:
Permissions and roles
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

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.


Related issues

Is duplicate of Redmine - Defect #25258: Field permissions ignored if the user and the group one belongs to share the same roleClosed

Actions
Actions

Also available in: Atom PDF