2.0, 1.6, Transactions not closing for LOST items once xact has been re-opened for modified billings.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned | ||
2.0 |
Fix Released
|
Undecided
|
Unassigned | ||
2.1 |
Fix Released
|
Undecided
|
Unassigned | ||
2.2 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Steps to replicate this issue,
Check-out an item and mark lost.
Add forgive payment to balance out bill.
At this point, the xact_finish is stamped and the xact is closed.
Check-in the item, returning it back to circulation.
If the void lost fee's on check-in is set in the org settings, then the xact is re-opened (xact_finish removed) and the lost fees and/or processing fees are voided, leaving a negative balance on the xact.
At this point, the lost item reappears in the Lost item section on the user account. Adding billings to make up for the negative balance will 0 out the balance, but the xact does not close.
Possible solution would be to have the system identify non-refundable payments related to lost fee's and void them at the time of check-in of a lost item.
Also the software needs to better handle the closing of transactions when the balance reaches 0, so they are not stuck open indefinitely.
Changed in evergreen: | |
importance: | Medium → High |
tags: | added: pullrequset |
tags: |
added: pullrequest removed: pullrequset |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
On a side note, if the item goes into the positive billing amounts and then brought down to 0, the transaction will close, it just appears to be if an item is in the negative, and then brought up to 0, it doesn't close.
So for example, the item above that is in a stuck state with 0 billings, I added a random bill amount to it which brought the item back to the bills screen. I then just simply voided out that bill, and then the transaction was closed and item removed from the lost list.