Uploaded image for project: 'ui-inn-reach'
  1. ui-inn-reach
  2. UIINREACH-16

INN-Reach General Settings: INN-Reach Compatible Locations

    XMLWordPrintable

    Details

    • Template:
      Front-end User Story Template
    • Sprint:
      Volaris Sprint 115
    • Story Points:
      5
    • Development Team:
      Volaris

      Description

      Purpose:

      Whereas FOLIO does not place character limits on location codes, INN-Reach has strict character limits on both codes and descriptions. Therefore, FOLIO locations must be mapped to INN-Reach compatible code and description combinations. These locations are configured tenant-wide, but mapped per central server.

      User story statement(s):

      As a FOLIO administrator with permission to edit INN-Reach locations,
      I want create, update, or delete an INN-Reach location code/description pair from INN-Reach settings,
      so that I can map my FOLIO locations to them in other parts INN-Reach settings.

      Scenarios:

      1. Scenario:
        • Given a user with permission to CRUD INN-Reach Locations (MODINREACH-17)
        • When I access the INN-Reach Settings in the Settings appĀ (UIINREACH-1)
        • Then there is an item under the "General" settings group for "INN-Reach Locations"
      2. Scenario
        • Given the previous scenario
        • When the users clicks on "INN-Reach Locations"
        • Then a detail/edit pane similar to that used for material types, loan types, and patron groups should appear with columns for Location code, description, last updated, and actions
      3. Scenario
        • Given the previous scenario
        • When the "+ New" button clicked
        • Then a new row is added to the list with editable form fields for location code and description, and save and cancel buttons
      4. Scenario
        • Given the previous scenario
        • When a user enters a valid location code (> 0 and <= 5 alphanumeric characters, unique) and description (> 0 and <=255 characters)
        • Then the "Save" button becomes active
      5. Scenario
        • Given the previous scenario
        • When the user clicks "Cancel"
        • The the fields are cleared and the new row is removed from the list
      6. Scenario
        • Given scenario 4
        • When the user clicks "Save"
        • Then the new location/description combination is saved to the backend and added to the list in alphabetical order by location code

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Igor Godlevskyi Igor Godlevskyi
                Reporter:
                brookstravis Brooks Travis
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases