Project

General

Profile

Actions

Defect #15988

closed

Unexpected behaviour on issue fields for users that have multiple roles

Added by VD DV almost 11 years ago. Updated almost 10 years ago.

Status:
Closed
Priority:
Normal
Category:
Issues workflow
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

To explain this possible defect let me explain this situation.
We have dozens of projects on which are defined mixed teams of users. We have defined roles for those projects&users.
I will focus on just those facts that matters this issue:
- We have one role that enables users to view just documents and nothing else (lets name it DocViewer).
- We have another role that enables user to report an issue and nothing else (lets name it IssueReporter).
- We have user (User1) that have both roles on some project
- We have defined field restrictions on workflow for IssueReporter on some field. For example we want to force users that owns role IssueReporter to fill some data at custom field (lets name it SomeRequiredField). That was done through workflow for role IssueReporter (on all trackers) by setting Requred attribute on SomeRequredField.

So we expected that User1 will be forced to fill up SomeRequiredField, but it is not happening. User1 still can skip that required field. Reason for this is that the User1 has also role DocViewer. Please note that this role have not any specific workflow nor field restrictions defined.

Conclusion:
It would be expected that roles that have not assigned permissions for adding or updating issues should not make any influence on field restrictions (and worflows also) in situations when user owns multiple roles.


Related issues

Related to Redmine - Defect #33059: "Role" dropdown in Workflow page is unexpectedly expanded when selecting "all"ClosedGo MAEDA

Actions
Related to Redmine - Defect #39493: Role with only :edit_own_issues no longer considered for workflowConfirmed

Actions
Precedes Redmine - Defect #34570: Misleading workflow/permission issueNew

Actions
Precedes Redmine - Defect #34284: In Role edit view the per tracker table only shows up when "View Issues" permission is selectedNew

Actions
Actions #1

Updated by VD DV over 10 years ago

Any updates on this issue? Is this defect fixed in recent Redmine versions?

Actions #2

Updated by Toshi MARUYAMA about 10 years ago

  • Subject changed from Unexpected behaviour on issue fiels for users that have multiple roles to Unexpected behaviour on issue fields for users that have multiple roles
Actions #3

Updated by VD DV almost 10 years ago

Can you reconsider fixing this Defect in near future?
In my opinion this defect is realy serious.

Actions #4

Updated by Toshi MARUYAMA almost 10 years ago

  • Target version set to 3.0.0
Actions #5

Updated by Jean-Philippe Lang almost 10 years ago

  • Assignee set to Jean-Philippe Lang
Actions #6

Updated by Jean-Philippe Lang almost 10 years ago

  • Status changed from New to Closed
  • Resolution set to Fixed
Actions #7

Updated by Go MAEDA over 4 years ago

  • Related to Defect #33059: "Role" dropdown in Workflow page is unexpectedly expanded when selecting "all" added
Actions #8

Updated by Mischa The Evil over 3 years ago

  • Precedes Defect #34570: Misleading workflow/permission issue added
Actions #9

Updated by Mischa The Evil over 3 years ago

  • Precedes Defect #34284: In Role edit view the per tracker table only shows up when "View Issues" permission is selected added
Actions #10

Updated by Mischa The Evil almost 1 year ago

  • Related to Defect #39493: Role with only :edit_own_issues no longer considered for workflow added
Actions

Also available in: Atom PDF