Content
Bug OP-8852: Editable/Visible checkboxes for a new custom field for User does not work/has no effect
View differences
Updated by Christophe Bliard over 2 years ago
### **Environment**:
**OpenProject 11.3.2 Community edition**
Windows / Chrome
### **Steps to reproduce:**
1. Go to Administration>>Custom Fields>>Users> New custom field
2. Create a format (Integer or Text), set Min length to 1, set Max length 10
3. Any default value
4. Required, Visible (checked)
5. Editable (unchecked)
6. Save
### **Actual Behavior**
Any user can edit and alter the value set by the administrator for the new custom field. field.
Any user can modify the value if he access My account from the Avatar menu and delete/modify and Save new value.
### **Expected Behavior**
User should not be allowed to alter the value set by and Administrator for that new custom field
### Acceptance Criteria
* For a user custom field with "editable" unchecked
* Adminitrators can edit it for other users
* Users with a "manage users" permission can edit it for other users
* When the field is required and does not have a default value, the user can edit it for themself
* When the field is required and has a default value, the user can **not** edit it (default value is used)
* When the field is not required, the user can **not** edit it
* For a user custom field with "visible" unchecked
* The field is not visible on users profile page
* The field is always visible in all user forms
* The UI text needs to be reworded to make it clearer
Note:
Windows / Chrome
### **Steps to reproduce:**
1. Go to Administration>>Custom Fields>>Users> New custom field
2. Create a format (Integer or Text), set Min length to 1, set Max length 10
3. Any default value
4. Required, Visible (checked)
5. Editable (unchecked)
6. Save
### **Actual Behavior**
Any user can edit and alter the value set by the administrator for the new custom field.
Any user can modify the value if he access My account from the Avatar menu and delete/modify and Save new value.
### **Expected Behavior**
User should not be allowed to alter the value set by and Administrator for that new custom field
### Acceptance Criteria
* For a user custom field with "editable" unchecked
* Adminitrators can edit it for other users
* Users with a "manage users" permission can edit it for other users
* When the field is required and does not have a default value, the user can edit it for themself
* When the field is required and has a default value, the user can **not** edit it (default value is used)
* When the field is not required, the user can **not** edit it
* For a user custom field with "visible" unchecked
* The field is not visible on users profile page
* The field is always visible in all user forms
* The UI text needs to be reworded to make it clearer
Note: