Details
-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
P3
-
Resolution: Done
-
Affects Version/s: None
-
Labels:
-
Template:customfield_11100 48847
-
Sprint:eHoldings Sprint 118
-
Story Points:0.5
-
Development Team:Spitfire
Description
Overview: ViewCustomFieldsRecord should not disappear when no custom-fields are present
Steps to Reproduce:
- Sign into folio-snapshot.dev.folio.org as a user with permission to manipulate custom fields (e.g. diku_admin)
- Visit Settings > Users > General | Custom fields
- Remove all custom fields
- Visit Users; in the User search pane, in the Status accordion, tick the 'Active' checkbox
- In the search results pane, click any user record
Expected Results:
- In the user details pane, an unlabeled pane below "Contact information" that shows the "loading" dots should eventually get a label
- If the accordion contains no content, the closed accordion should show a 0 badge, as do other accordions without content, e.g. Proxy/sponsor, Fees/fines.
- If the accordion contains no content, the opened accordion should show a "No ${foo}s found" message, as other accordions without content, e.g. Proxy/sponsor, Fees/fines.
Actual Results:
- In the user details pane, an unlabeled pane below "Contact information" shows the "loading" dots and then disappears
UX guidelines for interactive elements state that hiding elements should be based on permission (i.e. hide elements you don't have permission to use), and that when users have the necessary permission, elements should be displayed but disabled if necessary. To be consistent with other accordions and with these guidelines, ViewCustomFieldsRecord should always display.
TestRail: Results
Attachments
Issue Links
- clones
-
STSMACOM-470 ViewCustomFieldsRecord must never return an empty element (<>)
-
- Closed
-
- relates to
-
UXPROD-3166 Kiwi | Spitfire Tech debt
-
- Closed
-