Bug 39094 - Adjust system preferences to account for new option to refund the previous lost fee when marking an item Claims returned
Summary: Adjust system preferences to account for new option to refund the previous lo...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: System Administration (show other bugs)
Version: Main
Hardware: All All
: P5 - low minor
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 33292
Blocks:
  Show dependency treegraph
 
Reported: 2025-02-11 15:18 UTC by Emily Lamancusa (emlam)
Modified: 2025-03-18 19:06 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Emily Lamancusa (emlam) 2025-02-11 15:18:51 UTC
ClaimReturnedChargeFee has the option to charge a lost fee, don't charge, or ask if a lost fee should be charged, when marking an item claims returned. These options should be update to reflect the new option to refund the previous lost item fee.

Currently, if the preference is set to "ask if a lost fee should be charged", the modal shows two checkboxes: "Charge a lost fee" and "Refund previous lost fee". If the preference is set to charge or don't charge, the checkbox for "Charge a lost fee" is (correctly) not displayed, but the checkbox for "Refund previous lost fee" is also not displayed.

It's a bit odd to show either both checkboxes or neither. It would also be nice to have the same options for refunding the lost fee that we currently have for charging a lost fee (refund, don't refund, or ask). We should add more options to ClaimReturnedChargeFee, or add a ClaimReturnedRefundFee preference.

Somewhat relatedly, if we are going to allow the modal to give the user both options to charge or refund (or neither), we should use radio buttons or a drop-down in that case, rather than checkboxes, since it does not make sense to check both at once.