Uploaded image for project: 'ui-orders'
  1. ui-orders
  2. UIOR-377

Show indicator of open requests during receiving and check-in

    XMLWordPrintable

Details

    • Front-end User Story Template
    • ACQ Sprint 74
    • 2
    • Thunderjet

    Description

      Purpose: To show whether pieces (items) have open requests during the receiving/check-in process, so that they can be handled differently.

      As a staff person receiving or checking in a piece
      I want to see that a piece (usually corresponding to an "on order" item record in Inventory) has an open request on it
      So that I can choose to check in that piece first and possibly expedite its handling

      Scenarios

      1. Scenario 1
        • Given the Receiving Update details and Review details screens
        • When there is an open Request (Hold, Recall, Page) for any item record/piece
        • Then display "Yes" in a new Request column, as shown on the attached screenshot
      2. Scenario 2
        • Given the Check-in details screens
        • When there is an open Request (Hold, Recall, Page) for any item record/piece
        • Then display "Yes" in a new Request column, as shown on the attached screenshot
      3. Scenario 3
        • Given that receiving is complete
        • When there is an open request, display a modal, as shown in the attachment (2 versions - for single titles/barcodes or multiples)
          • Header: An item has an open request
          • [Title] ([Format]) (Barcode: [item barcode number] has an open request.
          • Button: Close
        • And require the user to close it before returning them to the receiving history
      4. Scenario 4
        • Given that check-in is complete
        • When there is an open request, display a modal, as shown in the attachment (2 versions - for single titles/barcodes or multiples)
          • Header: An item has an open request
          • [Title] ([Format]) (Barcode: [item barcode number] has an open request.
          • Button: Close
        • And require the user to close it before returning them to the check-in history
      5. Scenario 5
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      TestRail: Results

        Attachments

          1. Request-Awareness.png
            Request-Awareness.png
            379 kB
          2. Request-Awareness-Modal.png
            253 kB
          3. Request-Awareness-Modal-Multiple.png
            Request-Awareness-Modal-Multiple.png
            266 kB
          4. Request alert clarification.mp4
            6.77 MB
          5. Screen Shot 2019-10-18 at 11.35.23 AM.png
            Screen Shot 2019-10-18 at 11.35.23 AM.png
            132 kB
          6. Screen Shot 2019-10-18 at 11.31.27 AM.png
            Screen Shot 2019-10-18 at 11.31.27 AM.png
            101 kB
          7. ss.png
            ss.png
            44 kB
          8. Receiving with Requests.mp4
            7.61 MB

          Issue Links

            Activity

              People

                dennisbridges Dennis Bridges
                abreaux Ann-Marie Breaux
                Dennis Bridges Dennis Bridges
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases