https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28593 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomascohen@gmail.com --- Comment #1 from Tomás Cohen Arazi <tomascohen@gmail.com> --- This should be done on top of bug 28588, for sure. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28593 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |28588 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28588 [Bug 28588] Add Koha::Checkouts::ReturnClaim->resolve -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28593 --- Comment #3 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- It should be the replacement fee (plus processing fee, if any). We've got ClaimReturnedChargeFee with the options of do charge a fee, don't charge a fee, or give the choice to the user as they claim something. I'd like a parallel syspref for ClaimReturnedResolutionChargeFee with the options to charge, don't charge, or give the choice to the user as they resolve something. It should not ever create a *second* lost fee if the library is already charging at the point of Claim, and it should only charge at resolution if you're moving the item from Claims Returned to some other non-zero lost status. And the wording of the syspref should make that clear. "When resolving a claim and setting an item to lost (charge a lost fee / don't charge a lost fee / ask if a lost fee should be charged). If a fee was already generated based on ClaimReturnedChargeFee, this preference will not generate an additional fee." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28593 Azucena Aguayo <azucena.aguayo@uvu.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |azucena.aguayo@uvu.edu -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28593 snewell@hmcpl.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snewell@hmcpl.org -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28593 --- Comment #4 from hebah@bywatersolutions.com --- I was able, post 28271, to have this happen. Sort of. MarkLostItemsAsReturned has to exclude both when marking as claims return AND from items tab, and ClaimReturnChargeFee has to be set to Ask (I think - it was set that way already in my testing). 1. Mark checked out item as claim return, no charge. 2. See it's still on patron account. 3. From the item record, make the claim returned item Lost (or any other non-claim return lost status). 4. Go back to patron account and see item has been billed as lost like normal, claim return is still unresolved. Not a perfect metric and frankly doesn't really match with common MarkLostItemsAsReturned/ClaimReturnChargeFee settings for libraries that use claims return as customer service tool. Definitely more ideal to have third pref for claim return resolution tied to adding lost fee to account after grace period, since this is effectively a resolution of the CR status not addressed neatly without also touching the claim returns themselves. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.