Refund fees/fines: Report of refunds to process manually

Description

Purpose: Request refunds to process manually report for one date or date range.
Story: As a staff member who processes refunds, I need a list of refunds to be manually processed for patrons and transfer accounts.

Scenarios

  1. Scenario

    • Given the Users app Users search results page Actions drop-down

    • When open

    • Then show new drop-down option Refunds to process manually report (CSV) - see attached mock-up 1-users-actions-button.png

  2. Scenario

    • Given the Refunds to process manually report (CSV) option in Users app Users search results page Actions drop-down

    • When clicked

    • Then open Refunds to process manually modal (see attached mock-up 2-refunds-modal.png) with Save & close button inactive until Start date entered

  3. Scenario

    • Given the Refunds to process manually modal

    • When Cancel button pressed

    • Then close modal and return patron to Users app Users search results page

  4. Scenario

    • Given the Refunds to process manually modal

    • When Start date blank and End date not blank

    • Then display error: Must enter Start date if End date provided (and leave Save & close button inactive)

  5. Scenario

    • Given the Refunds to process manually modal

    • When Start date > End date

    • Then display error: End date must be after Start date (and leave Save & close button inactive)

  6. Scenario

    • Given the Refunds to process manually modal

    • When Start date not blank and End date blank

    • Then activate Save & close button

  7. Scenario

    • Given the Refunds to process manually modal

    • When Start date = End date

    • Then activate Save & close button

  8. Scenario

    • Given the Refunds to process manually modal

    • When Start date < End date

    • Then activate Save & close button

  9. Scenario

    • Given the Refunds to process manually modal

    • When Save & close button pressed

    • Then export a CSV file listing refunds to process manually with the start date entered or start-end date range provided (as shown in attachment 3-refunds-downloaded.png)

  10. Scenario

    • Given the Refunds to process manually report CSV file

    • When exported

    • Then export CSV file with columns as shown in attachment 4-refunds-to-process-manually.xlsx

Environment

None

Potential Workaround

None

Attachments

8
  • 15 Jan 2021, 02:52 PM
  • 15 Jan 2021, 02:52 PM
  • 05 Jan 2021, 05:45 PM
  • 05 Jan 2021, 05:44 PM
  • 13 Aug 2020, 08:26 PM
  • 13 Aug 2020, 08:12 PM
  • 30 Apr 2020, 07:19 PM
  • 30 Apr 2020, 07:19 PM

Checklist

hide

TestRail: Results

Activity

Show:

Holly Mistlebauer February 26, 2021 at 2:12 PM

Works as expected...thanks...

Holly Mistlebauer February 2, 2021 at 6:14 PM

: I have also created a user story (https://folio-org.atlassian.net/browse/UIU-2035#icft=UIU-2035) for messaging.

Holly Mistlebauer February 2, 2021 at 6:02 PM
Edited

: I just reported a third bug. It's https://folio-org.atlassian.net/browse/UIU-2034#icft=UIU-2034.

Holly Mistlebauer February 2, 2021 at 5:00 PM

: I found two bugs with the dates in the refund report criteria. I have reported them as UIU-2032 and https://folio-org.atlassian.net/browse/UIU-2033#icft=UIU-2033.
cc:

Holly Mistlebauer January 19, 2021 at 2:17 PM

, and : My plan was to test this today, before the sprint review, and close it. I won't be able to close this JIRA issue until I see the change from MODFEE-152 reflected here. It's my only way to confirm that MODFEE-152 is completed. Thanks...

Done

Details

Assignee

Reporter

Tester Assignee

Labels

Priority

Story Points

Sprint

Development Team

Vega

Fix versions

Release

R1 2021

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created August 21, 2019 at 4:40 PM
Updated March 18, 2021 at 11:11 PM
Resolved February 26, 2021 at 2:12 PM
TestRail: Cases
TestRail: Runs