1 - Place two holds for a patron
2 - Define a charge in ExpireReservesMaxPickUpDelayCharge
3 - Confirm both holds
4 - Cancel one hold from the patrons account page
5 - No charge
6 - Checkin the other waiting hold
7 - Click 'Cancel hold'
8 - Patron is charged
I can confirm that this bug is valid, because we exploit this as a workaround.
We wish for some patron categories to be charged the ExpireReservesMaxPickUpDelayCharge, and other patron categories to be exempt. This means we cannot cancel holds automatically, and we use this loophole so staff can charge some patron categories and not others.
This loophole won't be needed if bug 15561 enters Koha as the functionality to charge some patrons will be in the Holds Over tab: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15561
...but closing this loophole without the above bug would really affect our setup.
On the checkin screen, if ExpireReservesMaxPickUpDelayCharge is set, there is an option "Forgive fees for manually expired holds".
If ticked, the patron will not be charged.
Isn't it the expected behaviour?
Any updates on the 19486 bug?
Carnegie Stout Team would be grateful.
Is the bug here that cancelling the hold in the OPAC doesn't charge or is the bug that the fee is charged? The checkbox Jonathan decribes in comment#2 seems to cover that case.