https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34756
Tomás Cohen Arazi (tcohen) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Status|Signed Off |Failed QA --- Comment #19 from Tomás Cohen Arazi (tcohen) <[email protected]> --- I think this behavior should be baked into Koha::Hold->cancel. And tested. It seems that otherwise we will have to implement the same logic everywhere a hold cancellation happens (there are already comments about other places needing this treatment). As this is a behavior change, we will probably need to add a syspref or circ rule to control this, disabled by default. This could evolve -in separate report- into a more fine grained config. Do we have a way to know a transfer process has been initiated already? I imagine this can become problematic if the item is in a delivery truck already. not a blocker per se, just thinking out loud. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
