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

Support moving request above page

    XMLWordPrintable

Details

    • Story
    • Status: Open (View Workflow)
    • P4
    • Resolution: Unresolved
    • None
    • None
    • Vega

    Description

      Purpose: To handle the case of moving a request from source item to target when the moved request will jump a page request on the target item. This has some special handling needs and so was deprioritized for the first version of the move requests feature.

      Scenarios:

      1. Scenario
        • Given Request A is a Hold or Recall that was created at 10:00 on Item X
        • When Request A is moved to Item Y which has item status = Paged because it has also been requested (Request B, created at 10:30 am, Request status = Open - Not yet filled)
        • Then:
          • Request A should go to the top of the request queue for Item Y because it was created first and Request B has not yet begun fulfillment (this was working as of 2019-07-31)
          • Request A should automatically be changed to a Page request (popup should display letting user know)
          • Request B should be changed from Page request to Recall or Hold
            • A popup should display after the first popup allowing a user to choose which one
            • If selected type is allowed per request policy, success confirmation should display
            • If selected type is not allowed per request policy, see UIREQ-294 for desired behavior
          • Item status for Item X should not be impacted by the move of Request A (because only the presence of Page requests impacts item state and Request A was not a page request when it was created on Item X) (this is covered by CIRC-411)
      2. Scenario
        • Given Request A is a Page that was created at 10:00 on Item X
        • When Request A is moved to Item Y which has item status = Paged because it has also been requested (Request B, created at 10:30 am, Request status = Open - Not yet filled)
        • Then:
          • Request A should go to the top of the request queue for Item Y because it was created first and Request B has not yet begun fulfillment (this was working as of 2019-07-31)
          • Request A should remain a Page request (no popup needed here)
          • Request B should be changed from Page request to Recall or Hold
            • A popup should display after the first popup allowing a user to choose which one
            • If selected type is allowed per request policy, success confirmation should display
            • If selected type is not allowed per request policy, see UIREQ-294 for desired behavior
          • Item status for Item X should become Available if the request queue on Item X is now empty per CIRC-333 (this was working as of 2019-07-31)

      TestRail: Results

        Attachments

          1. screenshot-3.png
            screenshot-3.png
            18 kB
          2. screenshot-2.png
            screenshot-2.png
            19 kB
          3. screenshot-1.png
            screenshot-1.png
            19 kB

          Issue Links

            Activity

              People

                Unassigned Unassigned
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases