You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected Behavior (or desired behavior if a feature request)
A non-encrypted custom field values should be available for edition to a non-admin user.
Actual Behavior
Currently, when creating a non-encrypted custom field, only admin users are able to edit their values (except for lists, which seem to be working correctly)
Values can be correctly seen in the asset list view or when viewing the asset details, but not when editing (field is grayed out and shows "ENCRYPTED").
Please confirm you have done the following before posting your bug report:
Expected Behavior (or desired behavior if a feature request)
A non-encrypted custom field values should be available for edition to a non-admin user.
Actual Behavior
Currently, when creating a non-encrypted custom field, only admin users are able to edit their values (except for lists, which seem to be working correctly)
Values can be correctly seen in the asset list view or when viewing the asset details, but not when editing (field is grayed out and shows "ENCRYPTED").
Please confirm you have done the following before posting your bug report:
Please provide answers to these questions before posting your bug report:
app/storage/logs
and your webserver's logs.N/AThe text was updated successfully, but these errors were encountered: