https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16107 --- Comment #1 from Nicole C. Engard <nengard@gmail.com> --- Created attachment 49320 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=49320&action=edit print and confirm button -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16107 Owen Leonard <oleonard@myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|oleonard@myacpl.org |koha-bugs@lists.koha-commun | |ity.org Component|Templates |Hold requests CC| |gmcharlt@gmail.com --- Comment #3 from Owen Leonard <oleonard@myacpl.org> --- This happens because two things are going on at once, and Koha doesn't know how to prioritize which operation should be offered to the user. As far as I know, in order to reproduce this problem you have to do this: 1. Check in an item from Branch A at Branch B. This initiates a transfer between branches. 2. Place a hold on the item for a patron at any branch. Check in the item again. Because the transfer was initiated in step 1 Koha thinks it should remind you that a transfer is in progress and wants to to print a slip for that transfer (the "Print slip" link at the top of the screenshot). Because the item is also on hold for someone Koha prompts you to print a slip for the hold (the "Print slip and confirm" button in the screenshot). I'm inclined to think that the hold operation should take priority and the existing transfer should not get a prompt. However, a hold prompt would normally also have an "Ignore" option, which isn't present in this case. If you chose to ignore the hold, it seems logical that the transfer would then become an issue which should be prompted about. That's probably a matter of opinion, and I don't think there is an easy solution either way. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.