Uploaded image for project: 'ui-users'
  1. ui-users
  2. UIU-2705

Declared Lost/Aged to Lost: DO NOT BILL patron for ACTUAL COST of lost item

    XMLWordPrintable

Details

    • EPAM-Veg Sprint 156, EPAM-Veg Sprint 157
    • 2
    • Vega
    • Orchid (R1 2023)

    Description

      Purpose: Do not Bill the patron for the actual cost of a lost item.

      Story: As a staff member who charges patrons for lost items, I need to be able to not bill the patron for the actual cost of an item he/she lost even though we initially planned to.

      Scenarios:

      1. Scenario
        • Given Lost items requiring actual cost open and contains one or more items (as shown in attached mock-up 2-lost-items-requiring-actual-costs.png)
        • When ACTION ellipsis option "Do not bill" selected
        • Then open Do not bill <insert patron-last-name, patron-first-name patron-middle-name> modal (as shown in attached mock-up 9-do-not-bill-modal.png) with Continue button active, with these fields-
          • Fee/fine owner pre-populated and un-editable
          • Fee/fine type pre-populated and un-editable
          • Actual cost to bill patron required field that is set to zero
          • Additional information for staff non-required field that is set to the default of -
      2. Scenario
        • Given Do not bill <insert patron-last-name, patron-first-name patron-middle-name> modal open
        • When Cancel button pressed
        • Then close Do not bill <insert patron-last-name, patron-first-name patron-middle-name> modal, leaving user back at Lost items requiring actual cost
      3. Scenario
        • Given Do not bill <insert patron-last-name, patron-first-name patron-middle-name> modal_
        • When Continue button pressed
        • Then display Confirm no bill to be created for <insert patron-last-name, patron-first-name patron-middle-name> modal (as shown in attached mock-up 10-do-not-bill-confirm.png), with these fields-
          • No lost item fee will be charged to <insert patron-last-name, patron-first-name patron-middle-name> for <insert title and material type>. (for message line 1)
          • After the Confirm button is pressed, this cannot be undone. (for message line 2)
          • Additional information for staff pre-populated (if provided) and un-editable
      4. Scenario
        • Given Confirm no bill to be created for <insert patron-last-name, patron-first-name patron-middle-name> modal open
        • When Keep editing button pressed
        • Then close Confirm no bill to be created for <insert patron-last-name, patron-first-name patron-middle-name> modal, leaving patron back at Do not bill <insert patron-last-name, patron-first-name patron-middle-name> modal with these fields-
          • Fee/fine owner pre-populated and un-editable
          • Fee/fine type pre-populated and un-editable
          • Actual cost to bill patron required field that is set to zero
          • Additional information for staff optional field containing what was previously entered by the user, if anything
      5. Scenario
        • Given Confirm no bill to be created for <insert patron-last-name, patron-first-name patron-middle-name> modal open
        • When Confirm button pressed and another user has not edited the record
        • Then...
          • Close Confirm no bill to be created for <insert patron-last-name, patron-first-name patron-middle-name> modal, leaving user back at Lost items requiring actual cost
          • Display 'Success toast': A lost item fee will not be charged to <insert patron-last-name, patron-first-name patron-middle-name> (as shown in attached mock-up 11-do-not-bill-success.png)
          • Add Not billed in the Actions column (above ellipsis, as shown in attached mock-up 11-do-not-bill-success.png)
          • Gray out 'Bill actual cost' and "Do not bill" ellipsis options in the Actions column
          • Mark the actual cost record to be deleted when current user closes Lost items requiring actual cost (or however Vega decides to handle this)
      6. Scenario
        • Given Confirm no bill to be created for <insert patron-last-name, patron-first-name patron-middle-name> modal open
        • When Confirm button pressed and another user has edited the record
        • Then...
          • Close Confirm no bill to be created for <insert patron-last-name, patron-first-name patron-middle-name> modal, leaving user back at Lost items requiring actual cost
          • Display 'Error toast': <insert patron-last-name, patron-first-name patron-middle-name> has already been billed for this item by another user

      TestRail: Results

        Attachments

          1. 10-do-not-bill-confirm.png
            10-do-not-bill-confirm.png
            144 kB
          2. 11-do-not-bill-success.png
            11-do-not-bill-success.png
            143 kB
          3. 1-users-actions-updated.png
            1-users-actions-updated.png
            104 kB
          4. 2-lost-items-requiring-actual-costs.png
            2-lost-items-requiring-actual-costs.png
            153 kB
          5. 3-actual-cost-to-bill-modal.png
            3-actual-cost-to-bill-modal.png
            134 kB
          6. 4-modal-confirm.png
            4-modal-confirm.png
            143 kB
          7. 5-fee-charge-success.png
            5-fee-charge-success.png
            142 kB
          8. 6-show-long-title.png
            6-show-long-title.png
            150 kB
          9. 8-do-not-bill.png
            8-do-not-bill.png
            153 kB
          10. 9-do-not-bill-modal.png
            9-do-not-bill-modal.png
            138 kB
          11. C374125.mp4
            3.02 MB
          12. C375156.mp4
            2.91 MB
          13. C375161.mp4
            3.48 MB

          Issue Links

            Activity

              People

                Artem_Blazhko Artem Blazhko
                hollyolepm Holly Mistlebauer
                Holly Mistlebauer Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases