Close transactions after fines are voided,
Bug #965656 reported by
Steve Callender
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned |
Bug Description
This was tested in 2.0 and 2.1.
When fines are voided and the balance of a transaction hits 0, the transaction really should have the xact_finish timestamped to keep things uniform on the system.
A prime example here is when an item is checked in with a backdate and the system auto-voids the fines. The xact_finish is never stamped and the transaction remains open forever.
Same thing with manually voiding fines, it does not close the transaction.
This doesn't really impact the staff client billings view since 0 balance items will not be shown, but it does impact reporting.
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in evergreen: | |
importance: | Medium → Wishlist |
Changed in evergreen: | |
milestone: | none → 2.5.0-alpha1 |
Changed in evergreen: | |
milestone: | 2.5.0-alpha1 → 2.5.0-alpha2 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug also results in not being able to delete an account. A library attempting to delete an account ends up asking for assistance in order to have the transaction closed.