Uploaded image for project: 'ui-requests'
  1. ui-requests
  2. UIREQ-157

Paging Request Creation and Handling

    XMLWordPrintable

Details

    • Core: F - Sprint 58
    • 8
    • Prokopovych

    Description

      Purpose: To enable the creation of paging requests when item is available and to support In transit behavior for items with paging requests.

      User story:

      • As a user who wants to create a paging request
      • I want to be able to create that request for items that are Available in the library
      • So that the librarian can go get them off the shelf for me

      Scenarios:

      1. Scenario
        • Given Item X Status = Available
        • When a Request with Type = Page is created for Item X
        • Then:
          • Request should be successfully created
          • Request status should be "Open - Not yet filled"
          • Item status should become "Paged"
      2. Scenario
      3. Scenario
        • Given User A has a request on Item X with Pickup service point = SP1 AND User A's request is at the top of the request queue AND Item status = Paged
        • When Item X is checked in at a service point other than SP1
        • Then:
          • Generic in transit modal modal should display in check in app
          • Item status should change from "Paged" to "In transit"
          • Request status should change from "Open - Not yet filled" to "Open - In transit"
          • Hold shelf expiration date should not be set CB: Moved to UIREQ-144
      4. Scenario
        • Given User A has a request on Item X with Pickup service point = SP1 AND User A's request is at the top of the request queue AND Item status = Paged
        • When Item X is checked in at service point SP1
        • Then: CB: Should already be working per UICHKIN-50
          • "Awaiting pickup for a request" modal should display with
            • Title of modal: Awaiting pickup for a request
            • Body of modal: Place item <title of item> (<material type of item>) (Barcode: <barcode of item>) on hold shelf at <pick up service point> for request.
            • Controls:
              • Print slip - Checkbox (covered by UICHKIN-16)
              • Close - Button
              • X on window for closing (same as Close)
          • Item status should change from "Paged" to "Awaiting pickup"
          • Request status should change from "Open - Not yet filled" to "Open - Awaiting pickup"
          • Hold shelf expiration date should set to today's date + period (initially hardcoded to 14 days per UIREQ-144 but will eventually come from request policy) (covered by UIREQ-144)

      Additional scenarios to test, assuming the following stories are complete: UICHKIN-49, UICHKIN-50

      1. Scenario CB: No longer valid as page requests are only allowed on Available items
        • Given an Item X is in transit to home location (assumes there are no open requests)
        • When a page request is created on Item X
        • Then when Item X is next checked in, it will either be Awaiting pickup or In transit for a request (depending on the whether the check-in service point = the request pickup service point)
      2. Scenario CB: No longer valid as page requests are only allowed on Available items
        • Given an Item X is in transit or awaiting pickup for a request for User A
        • When a page request is created on Item X
        • Then when Item X is checked out to User A, the due date should be based on the loan policy (for Chalmers it will be 14 days per the loan/request policy setting "Alternate due date at checkout for items with existing requests") CB: Also, this loan policy setting has been replaced by other settings.

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                adityamatukumalli Aditya matukumalli
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases