Details
-
New Feature
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Duplicate
-
None
-
None
-
None
-
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
-
CIRC-397
[backend]Anonymize closed loans with fees/fines - exception for payment method
-
- Open
-
-
UITEN-40
Loan history settings: add exception for fee/fine action
-
- Closed
-
-
UITEN-59
Validation for loan history: exception for payment method settings
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
