Uploaded image for project: 'ui-checkin'
  1. ui-checkin
  2. UICHKIN-96

Multiple scans resulting in Recently returned

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Blocked (View Workflow)
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Template:

      Description

      Scenarios

      1. Scenario
        • Given an item with the status Recently returned, with no open requests, and a service point assigned to the item's effective location
        • When that item is checked in at that service point
        • Then the item's status should be Recently returned
          • Show item's status as Recently returned in check in history
          • In item details in Inventory, show item status as Recently returned
      2. Scenario
        • Given an item with no requests that has been checked in at service point Y assigned to its effective location at time A, resulting in a status of Recently returned
        • When that item, still with status Recently returned and no requests, is checked in at service point Y at time B
        • Then change the item's status from Recently returned to Available relative to time B + shelving lag time for service point Y
          • In item details in Inventory, show item status as Available
          • In item details in Inventory, show item status date as time of change
      3. Scenario
        • Given an item with no requests that has been checked in at service point Y assigned to its effective location at time A, resulting in a status of Recently returned
        • When that item, still with status Recently returned and no requests, is checked in at service point Z (also assigned to its effective location) at time B
        • Then change the item's status from Recently returned to Available relative to time B + shelving lag time for service point Z
          • In item details in Inventory, show item status as Available
          • In item details in Inventory, show item status date as time of change

      Notes Some systems consider the second (or nth) scan to be a status change, since it restarts the clock, even though the status itself doesn't change.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                ecboettcher Emma Boettcher
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases