Uploaded image for project: 'Library Apps'
  1. Library Apps
  2. LIBAPP-94

UX: Field-Level Validation

    XMLWordPrintable

Details

    • LIBAPP Sprint 8

    Description

      What do field-level validation errors look like? Filip had mentioned toast notifications for some things, but for field validation, there probably needs to be an error right next to/above the invalid field? Maybe in red?

      TestRail: Results

        Attachments

          1. 007_validation.gif
            007_validation.gif
            44 kB
          2. validation_0000_neutral.jpg
            validation_0000_neutral.jpg
            193 kB
          3. validation_0001_all error.jpg
            validation_0001_all error.jpg
            218 kB
          4. validation_0002_error mouse over.jpg
            validation_0002_error mouse over.jpg
            236 kB
          5. validation_0003_error focus.jpg
            validation_0003_error focus.jpg
            237 kB
          6. validation_0005_error correcting.jpg
            validation_0005_error correcting.jpg
            217 kB
          7. validation_0006_success.jpg
            validation_0006_success.jpg
            217 kB

          Issue Links

            blocks

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LIBAPP-116 UI: Field Level Validation Indicator

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LIBAPP-116 UI: Field Level Validation Indicator

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Umbrella - FOLIO-481 Design APIs for field-level validation errors

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LIBAPP-114 Validate Last Name and User ID (Username)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                filipjakobsen Filip Jakobsen
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases