Uploaded image for project: 'ui-tenant-settings'
  1. ui-tenant-settings
  2. UITEN-16

Loan history settings (anonymize closed loans with fees/fines - exception for payment method)

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      Concorde - Sprint 67
    • Story Points:
      8
    • Development Team:
      Concorde

      Description

      Purpose: Create settings in UI for users to anonymize closed loans.

      As a staff member, I want loans with fines and fees to be anonymized based on different criteria than other loans, so that the library doesn't lose important financial information so that their circulation history is private & the library complies with regulations on privacy.

      Scenarios

      1. Scenario
        • Given the Settings/Circulation/Loan History
        • When "Treat closed with associated fees/fines differently" is checked
        • Then show the Closed loans with associated fees/fines section
          • Heading: Closed loans with associated fees/fines
          • Body: Anonymize closed loans with associated fees/fines:
          • Radio buttons:
            • Immediately after fee/fine closes
            • <field accepting integers> <dropdown menu for Day(s), Week(s), Month(s), default: Select interval> after fee/fine closes
            • Never
          • Header: Exception for payment method
            • Button: Add exception (note that the mockup has "+ Add exception", but "+" should not be part of the label)
      2. Scenario
        • Given the Closed loans with associated fees/fines section
        • When the user selects Add exception
        • Then complete the Exception for payment method section
          • Header: Exception for payment method
          • Dropdown: Setting for payment method
            • Values: All payment methods listed under Users/Payment methods
            • Default: Select payment method
          • Radio buttons:
            • Immediately after fee/fine closes (note that this is different from what's shown on mock)
            • <field accepting integers> <dropdown menu for Day(s), Week(s), Month(s), default: Select interval> after fee/fine closes (note that this is different from what's shown on mock)
            • Never
          • Trash can icon (next to dropdown menu)
          • Button: add exception
      3. Scenario
        • Given the Exception for payment method section
        • When the user clicks the trash can icon
        • Then delete the exception for the payment method
      4. Scenario
        • Given the Exception for payment method section
        • When the user has made changes
        • Activate the Save button
      5. Scenario
        • Given the Exception for payment method, with changes made
        • When the user attempts to navigate away
        • Then show the unsaved changes modal
      6. Scenario
        • Given the Exception for payment method, with the <X time> after loan closes radio button selected
        • When the inputs are invalid:
          • No value, non-integer or negative number in <field accepting integers>
          • Dropdown menu set to Select interval
        • Then do not allow the user to save
      7. Scenario
        • Given the Exception for payment method section
        • When the user has selected the same payment method for multiple exceptions
        • then do not allow the user to save

        TestRail: Results

          Attachments

          1. 1-Loan-History.png
            1-Loan-History.png
            78 kB
          2. 2-Loan-History.png
            2-Loan-History.png
            82 kB
          3. 3-Loan-History.png
            3-Loan-History.png
            96 kB
          4. 4-Loan-History.png
            4-Loan-History.png
            109 kB
          5. 5-Loan-History.png
            5-Loan-History.png
            108 kB
          6. 6-Loan-History.png
            6-Loan-History.png
            108 kB
          7. 7-Loan-History.png
            7-Loan-History.png
            121 kB

            Issue Links

              Activity

                People

                Assignee:
                ecboettcher Emma Boettcher
                Reporter:
                ecboettcher Emma Boettcher
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases