Fees/Fines
(UXPROD-792)
|
|
| Status: | Open |
| Project: | ui-inventory |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Fees/Fines |
| Type: | Story | Priority: | P3 |
| Reporter: | Erin Nettifee | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | feesfines | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Sprint: | |||||||||||||
| Development Team: | Prokopovych | ||||||||||||
| Release: | Not Scheduled | ||||||||||||
| Epic Link: | Fees/Fines | ||||||||||||
| RCA Group: | TBD | ||||||||||||
| Description |
|
Current situation or problem: Right now, patrons with appropriate permissions can delete item records in Inventory, with dependency checks on certain transactions (see
This feature covers implementation of dependency checks for fee/fines. An item may have an associated unpaid or unresolved fee/fine even if the item is available and/or does not have an active loan. This occurs with overdue or overdue recall fines, where items can circulate to multiple users and accrue fines without ever becoming lost. So the dependency check must actively check fine records, not just item statuses like 'declared lost' or 'aged to lost'. In scope
Out of scope Use case(s) Proposed solution/stories Links to additional info
Questions
|
| Comments |