https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25726 --- Comment #4 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Me, too! We've only seen a couple examples and haven't yet tracked down how they got in that state. In both cases the hold had a reserves.found value of T, but was not actually in transit. In one of those cases, the patron had 2 holds on the same record, which suggests maybe bug 18958 is involved? But, yes, for sure, there is a larger issue of where this bad data came from, my patch is just alleviating the major symptom caused by the data's existence. (In reply to Katrin Fischer from comment #3)
Hi Andrew,
I am a bit worried about the cause of these strange holds. You say reserves.found is not null - what was the found value for these strange holds?
-- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.