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

Request Move: Allow Type Change When Current Type is Prohibited by Policy

    XMLWordPrintable

Details

    • Story
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Done
    • None
    • 1.12.0
    • None
    • Core: F - Sprint 67, Core: F - Sprint 68, Core: F - Sprint 69, Core: F - Sprint 70
    • 5
    • Prokopovych

    Description

      Purpose: We implemented basic request moving as part of UIREQ-269 and, in testing, I realized that one scenario was more limiting than users would want it to be. The purpose of this story is to allow librarians to change the request type if the current type is not allowed for the target item.

      User story:
      As a librarian who is attempting to move a request to an item for which that type of request is prohibited by policy
      I want to be have the option to change the request type to something that is allowed, if possible
      So I can process the request without having to cancel and recreate (which will send notifications to the patron and disrupt the order of requests)

      Scenarios

      1. Scenario
        • Given I attempt to move a request AND current request type is not allowed per applied request policy AND "Request not allowed for this patron/item" modal displays
        • When the "Request not allowed for this patron/item" modal is closed
        • Then user is allowed to try again by selecting another type of request from those allowed per the request whitelist. CB: I am not being given the chance to select a different type so I can move the request. See screencast: https://www.screencast.com/t/pHbx55NC1kb
      2. Scenario
        • Given scenario 1
        • When newly selected type is also disallowed per policy
        • Then system will generate another "request type not allowed for this item/patron combo" popup and user is out of luck (can't move the request to this item)
          • NOTE: This is already working when you move a page request to an item that is not available - we just need to make it work for situations when you are moving a hold or recall to an item that is not available
      3. Scenario
        • Given scenario 1
        • When selected type IS allowed per policy
        • Then the request should be moved and converted to the selected type
      4. Scenario
        • Given scenario 4
        • When selected type is a recall AND target item is a Checked out item which hasn't already been recalled
        • Then the target item should be recalled (this should already work per CIRC-316, I am just putting it here for testing purposes)

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                mpk35 Michal Kuklis
                cboerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases