[Bug 19486] New: When cancelling a waiting hold via circulation the patron is charged the ExpireReservesMaxPickUpDelayCharge
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19486 Bug ID: 19486 Summary: When cancelling a waiting hold via circulation the patron is charged the ExpireReservesMaxPickUpDelayCharge Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs@lists.koha-community.org Reporter: nick@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, kyle.m.hall@gmail.com 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 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19486 Sally Healey <sally.healey@cheshiresharedservices.gov.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sally.healey@cheshireshared | |services.gov.uk --- Comment #1 from Sally Healey <sally.healey@cheshiresharedservices.gov.uk> --- 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. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19486 Jonathan Druart <jonathan.druart@bugs.koha-community.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart@bugs.koha-c | |ommunity.org --- Comment #2 from Jonathan Druart <jonathan.druart@bugs.koha-community.org> --- 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? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19486 Brian <bklein@dubuque.lib.ia.us> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bklein@dubuque.lib.ia.us --- Comment #3 from Brian <bklein@dubuque.lib.ia.us> --- Any updates on the 19486 bug? Carnegie Stout Team would be grateful. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19486 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #4 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- 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. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org