Uploaded image for project: 'ui-users'
  1. ui-users
  2. UIU-2210

ViewCustomFieldsRecord must never return an empty element (<>)

    XMLWordPrintable

Details

    • eHoldings Sprint 118
    • 0.5
    • Spitfire

    Description

      Overview: ViewCustomFieldsRecord should not disappear when no custom-fields are present
      Steps to Reproduce:

      1. Sign into folio-snapshot.dev.folio.org as a user with permission to manipulate custom fields (e.g. diku_admin)
      2. Visit Settings > Users > General | Custom fields
      3. Remove all custom fields
      4. Visit Users; in the User search pane, in the Status accordion, tick the 'Active' checkbox
      5. In the search results pane, click any user record

      Expected Results:

      1. In the user details pane, an unlabeled pane below "Contact information" that shows the "loading" dots should eventually get a label
      2. 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.
      3. 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:

      1. 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

            Activity

              People

                kgambrell Khalilah Gambrell
                mariiaschv Mariia Sychova
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases