Defect #13926

Changing field permissions doesn't affect all users

Added by Dzianis Frydliand over 4 years ago. Updated over 4 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Permissions and roles
Target version:-
Resolution:Duplicate Affected version:

Description

Hi everyone!

We've been using Redmine for half a year and a little time ago have decided to change some workflow stuff.
At the 'Field Permissions' tab we have made some fields required for certain roles. But we've noticed that the changes didn't apply to all users of this role.

After investigating we've found out that this issue applies only for administrators accounts. Is that correct that administrators can leave required fields blank?

We don't have an administrator in our team, so project manager has administrator access to Redmine. And also this PM creates tasks so it's crucial for us that workflow should also apply to PM's account discarding it's administrator's status.

Versions info:

Environment:
  Redmine version                          2.3.0.stable.11715
  Ruby version                             2.0.0 (x86_64-linux)
  Rails version                            3.2.13
  Environment                              production
  Database adapter                         Mysql2
Redmine plugins:
  redmine_mylyn_connector                  2.8.2.stable


Related issues

Duplicates Redmine - Defect #11887: Issue permission doesn't apply to Administrators New

History

#1 Updated by Dzianis Frydliand over 4 years ago

Any comments on this issue?

#2 Updated by Daniel Felix over 4 years ago

Hi,

yes this is the right behaviour.

An Administrator must be able to clean out values from some fields, even if he don't know what the right value for this fields is.

The normal behaviour is, that only a few persons has admin privileges. In the best case on separate user accounts.

Admins will bypass every restriction.

Best regards,
Daniel

#3 Updated by Daniel Felix over 4 years ago

  • Category set to Permissions and roles
  • Resolution set to Invalid

#4 Updated by Dzianis Frydliand over 4 years ago

  • Status changed from New to Resolved

Thank you for the response!

#5 Updated by Daniel Felix over 4 years ago

  • Status changed from Resolved to Closed

Thanks. Just a suggestion. Try to give your admins separate accounts, otherwise the workflow won't fit to them as expected. This is the way, we handle this.

#6 Updated by Mischa The Evil over 4 years ago

For referencing purposes: #11887.

#7 Updated by Mischa The Evil over 4 years ago

  • Resolution changed from Invalid to Duplicate

Also available in: Atom PDF