From acd4b21c91f4b06a6e19cafb4b9a6dd2817ad8e9 Mon Sep 17 00:00:00 2001 From: Kyle M Hall Date: Wed, 22 May 2013 09:52:40 -0400 Subject: [PATCH] Bug 10311 - Holds queue ignores item-level holds where only one items exists If a record has only one item, and that item has one item-level hold on it, that hold will not show in the holds queue. Test Plan: 1) Create 1 record with 1 item at BranchA 2) Create an item-level hold for that item, for pickup at BranchA by a patron of BranchA 3) Run build_holds_queue.pl 4) View the holds queue for BranchA 5) Note the hold is not in there 6) Apply this patch 7) Re-run build_holds_queue.pl 8) View the holds queue again 9) Not that the hold is now there Signed-off-by: George Williams Signed-off-by: Chris Cormack Signed-off-by: Galen Charlton --- C4/HoldsQueue.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/C4/HoldsQueue.pm b/C4/HoldsQueue.pm index dc43113f0b..2052f096c7 100755 --- a/C4/HoldsQueue.pm +++ b/C4/HoldsQueue.pm @@ -406,7 +406,7 @@ sub MapItemsToHoldRequests { push @{ $items_by_branch{ $item->{holdingbranch} } }, $item unless exists $allocated_items{ $item->{itemnumber} }; } - return unless keys %items_by_branch; + return \%item_map unless keys %items_by_branch; # now handle the title-level requests $num_items_remaining = scalar(@$available_items) - scalar(keys %allocated_items); -- 2.39.5