I have created a normal dropdown custom field, two organizations: one can edit it and the other can not edit it, only view (field level permissions), and one project: some users can only report and others can edit/add (project permissions).
So, the problem is one user who can edit the custom field (field level permissions) but only can report (project permissions), can "edit" the custom field, but... he only can report! the word "edit" between quotes because the action is registered in the change history and the message is successful but the value never changes in the database. I would expect the same behaviour of default fields or even the project custom fields.
I have no idea how set the permissions, in order to the user who can only report, can not edit the custom field until he has the edit/add project permission.
Any idea?
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have created a normal dropdown custom field, two organizations: one can edit it and the other can not edit it, only view (field level permissions), and one project: some users can only report and others can edit/add (project permissions).
So, the problem is one user who can edit the custom field (field level permissions) but only can report (project permissions), can "edit" the custom field, but... he only can report! the word "edit" between quotes because the action is registered in the change history and the message is successful but the value never changes in the database. I would expect the same behaviour of default fields or even the project custom fields.
I have no idea how set the permissions, in order to the user who can only report, can not edit the custom field until he has the edit/add project permission.
Any idea?
Thanks.
You might have found a bug...
Hi,
any solution?
I have the same issue with a project...
I changed user permissions but the custom fields are still editable from everybody!