Uploaded image for project: 'mod-circulation-storage'
  1. mod-circulation-storage
  2. CIRCSTORE-110

Implement request status "Closed - Unfilled"

    XMLWordPrintable

Details

    • EPAM-Veg Sprint 9, EPAM-Veg Sprint 10
    • 3
    • Vega
    • Small < 3 days
    • We need to consult Jakub
    • Very Small (VS) < 1 day

    Description

      Purpose: To enable requests to expire based on the Request expiration date, which results in the new request status "Closed - Unfilled"

      User story:
      As a user who needs a book by a certain date but, after that date, the book will no longer be useful to me
      I want to set an expiration date for my request
      So that, if the date passes and I still haven't received the book, my request will automatically close (as I really no longer need it)

      Scenarios:

      1. Scenario
        • Given a request with request status = "Open - Not yet filled"
        • When the request's "Request expiration date" passes
        • Then:
          • The request status should change to "Closed - Unfilled"
          • The request is removed from the queue for the item by
            • removing it's position
            • re-positioning all other requests in the queue accordingly
          • The item status of the associated item should not change
          • No edit button or other edit option should appear (closed requests should never be editable)
      2. Scenario
        • Given requested item A with request status "Closed - Unfilled"
        • When item A is checked in
        • Then check in should behave as it would if the closed request weren’t present - I will add some test scenarios to elaborate on how that logic should work)

      Test Scenarios (to elaborate on scenario 2 above)
      This functionality already works, we just need to make sure it still works in this new scenario

      1. Scenario
        • Given a requested item A with Item status = Checked out AND Request X is in position 1 of the request queue and Request Y is in position 2 of the request queue
        • When Request X becomes "Closed - Unfilled" AND Item A is checked in at Service Point 1
        • Then:
          • Item status will change to Awaiting pickup if Request Y has pickup service point Service Point 1
          • Item status will change to In transit if Request Y has pickup service point other than Service Point 1
      2. Scenario
        • Given a requested item A with Item status = Checked out AND Request X is in position 1 of the request queue AND there are no other requests in the request queue for that item
        • When Request X becomes "Closed - Unfilled" AND Item A is checked in at Service Point 1
        • Then:
          • Item status will change to Available if Item A's Effective location is related to Service Point 1
          • Item status will change to In transit if Item A's Effective location is not related to Service Point 1
      3. Scenario
        • Given a requested item A with Item status = Paged AND Request X is in position 1 of the request queue AND there are no other requests in the request queue for that item
        • When Request X becomes "Closed - Unfilled" AND Item A is checked in at Service Point 1
        • Then:
          • Item status will change to Awaiting pickup if Item A's Effective location is related to Service Point 1
          • Item status will change to In transit if Item A's Effective location is related to a service point other than Service Point 1

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                cboerema Cate Boerema
                cboerema Cate Boerema
                Tania Fersenheim Tania Fersenheim
                Matt Connolly Matt Connolly
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases