Project

General

Profile

Actions

Defect #29742

closed

Conflict with rights and roles.

Added by Andrey Lobanov (RedSoft) about 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Permissions and roles
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Wont fix
Affected version:

Description

In our tracker we have 2 typical roles: 'Participant' and 'Developer'.
Role 'Participant' have rights for reading and changing issues and etc. But role 'developer' have some required custom fields. And if user have both of this roles then required fields is ignored. I think this is wrong behaviour. If 'developer' have some required field then 'participant' role must follow this rule.

Actions #1

Updated by Holger Just about 6 years ago

  • Status changed from New to Closed
  • Resolution set to Wont fix

Redmine generally allows the least-restrictive rules to apply for these editing permissions.

Thus, if a user is allowed to leave a field blank in any of their roles, it is not required for them. The same rule applies to the "readonly" setting. If any of the user's roles allows to edit a field, they can edit it. Only if all roles enforce a read-only setting, they can't change the field.

This is consistent with the behavior for Administrators who are considered to have all possible roles in a project in this regard. Thus, Administrators are only forced to fill a field if it is required for all roles in your Redmine installation.

Actions

Also available in: Atom PDF