Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2069

Anonymizing closed loans through settings: exception for fee/fine action

    XMLWordPrintable

Details

    • XL < 15 days
    • Vega
    • 38
    • R5
    • R4
    • R2
    • R4
    • R2
    • R4
    • R4
    • R4
    • R4
    • R3
    • R3

    Description

      Current situation or problem:
      As of Fameflower, users can configure anonymization settings so that loans without associated fees/fines are anonymized on a different schedule than loans with associated fees/fines. For example, a user can configure loans without fees/fines to be anonymized a week after the item is checked in, but anonymize a loan with an associated fee/fine a year (or never, or some other interval of time) after that fee/fine is closed.

      The same group of settings also has a UI differentiating anonymization by payment method, but these settings are inactive.

      In scope

      • Relabel "payment method" in those settings "fee/fine action"
      • Implement logic to make those settings active

      Out of scope

      Use case(s)

      Proposed solution/stories

      Links to additional info

      Questions

      • If different fee/fine actions are applied to the same fee/fine or on fees/fines for the same loan, which setting takes precedence?

      TestRail: Results

        Attachments

          Issue Links

            is defined by

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-397 [backend]Anonymize closed loans with fees/fines - exception for payment method

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UITEN-40 Loan history settings: add exception for fee/fine action

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UITEN-59 Validation for loan history: exception for payment method settings

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            New Feature - New feature requests UXPROD-447 Retain loan and item information for closed loans with fees/fines

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-1085 Automatically Anonymizing/Scrubbing Loan Data (through Settings)

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests UXPROD-2068 Anonymizing closed loans through settings

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                cmalmbor Cheryl Malmborg
                ecboettcher Emma Boettcher
                Marc Johnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases