To recreate: 1 - Backup your db (or not, I am not your parent) 2 - Set some items as withdrawn (UPDATE items SET withdrawn = 1) 3 - Try to place some holds 4 - The screen says no items are available, but it is hard to see why 5 - Restore your database, or just live your life :-)
This is a hard one, we reject the hold because of IsAvailableForItemLevelRequest, which is very poorly written...
I think this is a valid bug. Koha recently made the item display as Damaged if it were in fact damaged when placing a hold and this allows staff to see that the item that is possibly being placed on hold is Withdrawn.
Created attachment 98370 [details] [review] Bug 20708: Add Withdrawn status when placing a request in staff Same as bug 22021 for the withdrawn status. 1. Withdraw an item 2. Place an hold on this item Notice the new "withdrawn" status in the information column
Created attachment 98386 [details] [review] Bug 20708: Add Withdrawn status when placing a request in staff Same as bug 22021 for the withdrawn status. 1. Withdraw an item 2. Place an hold on this item Notice the new "withdrawn" status in the information column Signed-off-by: Nick Clemens <nick@bywatersolutions.com>
Trivial patch, works well, passing QA
Nice work everyone! Pushed to master for 20.05
Pushed to 19.11.x branch for 19.11.03
Doesnt apply clean to 19.05.x, no backport