Uploaded image for project: 'ui-checkout'
  1. ui-checkout
  2. UICHKOUT-677

Item blocks: Allow for override when logged in user has credentials

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: P2
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 6.0.0
    • Labels:
      None
    • Template:
    • Sprint:
      EPAM-Veg Sprint 100, EPAM-Veg Sprint 104, EPAM-Veg Sprint 106, EPAM-Veg Sprint 107, EPAM-Veg Sprint 108
    • Story Points:
      5
    • Development Team:
      Vega

      Description

      Overview:
      This is the first part of the item block override, which is the case when the logged in user has the credentials to do the override. When is determined that checking out the item will be blocked, the logged in user's credentials will be checked. If they have the item block override credential, the Override button will appear in the item block modal. If they do not, only the Close button will appear. In the future, instead of just displaying the Close button, we will display a modal that allows for a supervisor item block override code to be entered. This is user story UIU-1288.

      Scenarios:

      1. Scenario
        • Given patron has reached item block limit and logged in user does have permission User: Can override item blocks
        • When modal 'Item not checked out' displays
        • Then add Override button to the left of the current Close button (as shown in attachments Updated-item-block-modal.jpg and New-item-block-modal-example.jpg)
      2. Scenario
        • Given 'Item not checked out' modal (Scenario 1 above)
        • When Close button is clicked
        • Then close 'Item not checked out' modal without checking out the item to the patron
      3. Scenario
        • Given 'Item not checked out' modal (Scenario 1 above)
        • When the Override button is clicked
        • Then display ‘Override item block’ modal (as shown in attachment Enter-override-comment-format.jpg (Enter-override-comment-example.jpg shows an example) where -
          • XXXXXXXXXXXXXXXXXXXXXXXX = Instance (aka title)
          • ZZZZZZ = Material type
          • 999999999 = Item barcode
          • Save & close button is grayed out
      4. Scenario
        • Given ‘Override item block’ modal (Scenario 3 above)
        • When the Cancel button is clicked
        • Then close ‘Override item block’ modal without checking out the item to the patron (go back to Checkout page)
      5. Scenario
        • Given ‘Override item block’ modal (Scenario 3 above)
        • When required field Comment entered
        • Then activate Save & close button
      6. Scenario
        • Given ‘Override item block’ modal with Save & Close button activated (Scenario 5 above)
        • When the Save & close button is clicked
        • Then:
          • Close ‘Override item block’ modal (going back to Checkout page)
          • Check out item to patron
          • Create usual Loan Record/Loan Action Record that has Action set to 'Checked out through override' and Comment set to what was entered as a Comment on the ‘Override item block’ modal (see override of non-loanable item as example)
          • Display* (Item limit overridden)* under Loan Policy on Scanned items page (as shown in attachment New-scanned-items-list.jpg)
      7. Scenario
        • Given patron has reached item block limit and logged in user does NOT have permission User: Can override item blocks
        • When modal 'Item not checked out' displays
        • Then display modal with just Close button as is currently done (as shown in attachment Current-item-block-modal.jpg)

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                annamelnyk Anna Melnyk
                Reporter:
                hollyolepm Holly Mistlebauer
                Tester Assignee:
                Darcy Branchini Darcy Branchini
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases