Red Hat Bugzilla – Bug 1026899
[Usability] Provide "lock" icons for read-only form modes as well
Last modified: 2015-02-01 20:24:04 EST
When attributes are not writable, the various edit forms show the lock icon next to the attribute. The "read" views for resources should do the same for attributes that are not readable, to give the user a better indication that the empty value displayed may not be the actual value.
In agreement with Catherine we've decided that UX issues will be tracked separately.
Issue moved under the UX component.
Also moved to 6.4 as this issue is still valid for 6.3. Use ack flags to decide whether we want to go through with it or not.
UX will look at improving this editing and viewing flow for 'locked' fields in EAP 7.
Would it be possible to get a screenshot of this?
Created attachment 926194 [details]
screen shot of writing datasource security
Attached screenshot of editing attributes for a datasource when in a role that doesn't allow modification of those particular attributes. Lock icons are visible.
Created attachment 926195 [details]
screen shot of reading datasource security
Attached screen shot of just reading those same attributes. No lock icons visible. The attributes actually have values, but they are not shown because the user does not have permission to read them.
Created attachment 926545 [details]
Some alternative solutions, please refer to the attachment.
Option 1 – If NONE of the fields can be viewed or edited, it seems better to just provide an inline information message, rather than a form/table with “empty” values. The inline message would allow the user to quickly understand what the issue is. And it could even offer suggestions for resolution (log back with under a different role?).
Option 2 – If SOME of the fields can be viewed/edited:
* Alternative A) Hide the fields that the user is not allowed to see. And offer some inline help text to explain that the permissions are limiting the view.
* Alternative B) If showing the fields that the user does not have permissions to, is helpful to the user by providing context or additional information – then: Gray-out the fields that the user cannot view or edit, and provide some inline help text for each row.
ad Option 2 option B)
This is partially what we are doing currently. If user edits the form and doesn't have the permission the field is Grayed-out. With that part I am quite OK. The real problem is reading the value out of edit mode. Unless some further information (e.g. the lock icon) is provided there is no way to know whether the value is empty or whether i simply don't have the permissions to read it (unless I switch to edit mode).
Let's keep it simple and go for alternative B
Heiko Braun <email@example.com> updated the status of jira HAL-294 to Resolved
Should this still remain in POST state?