http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13153 Bug ID: 13153 Summary: Waiting hold checked in at different library doesn't re-route item to correct library Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs@lists.koha-community.org Reporter: kyle@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com It seems that if an item is triggered at a location as waiting for pickup, if that item falls into the hands of another library by mistake, Koha doesn’t know what to do with it. It just records a local use. It doesn’t try to transfer home or to the library it should be waiting at. Correct behavior should be that if it is scanned at another location other than where the system thinks it is, it should trigger a transfer to where it should be. Right now, the only way to get the item back on course is to go to the holds for that item and change the waiting to priority 1 again, and change any other priorities back one level, if any, and then check the item in again. To reproduce: 1) Place a hold on an item for a patron at LibraryA 2) Check the item in at LibraryA 3) Confirm the hold at LibraryA, the item is now a waiting hold 4) Set your logged in branch to LibraryB 5) Check the item in at LibraryB 6) Notice there is no request to transfer the item to LibraryA I think what should probably happen is the hold status should go from Waiting (W) to In Transit (T), and a transfer should be created. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.