Bug 19486 - When cancelling a waiting hold via circulation the patron is charged the ExpireReservesMaxPickUpDelayCharge
Summary: When cancelling a waiting hold via circulation the patron is charged the Expi...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: master
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-18 15:41 UTC by Nick Clemens
Modified: 2020-01-11 20:18 UTC (History)
6 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Clemens 2017-10-18 15:41:44 UTC
To recreate:
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
Comment 1 Sally 2017-10-19 11:26:27 UTC
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.
Comment 2 Jonathan Druart 2017-10-26 18:36:01 UTC
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?
Comment 3 Brian 2018-11-01 19:46:12 UTC
Any updates on the 19486 bug?

Carnegie Stout Team would be grateful.
Comment 4 Katrin Fischer 2020-01-11 20:18:03 UTC
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.