Summary: | Automatic transfer shouldn't take precedence over a hold transit | ||
---|---|---|---|
Product: | Koha | Reporter: | Liz Rea <wizzyrea> |
Component: | Hold requests | Assignee: | Galen Charlton <gmcharlt> |
Status: | CLOSED WORKSFORME | QA Contact: | Bugs List <koha-bugs> |
Severity: | normal | ||
Priority: | P5 - low | CC: | george, martin.renvoize, veron, wizzyrea |
Version: | rel_3_2 | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 22162 | ||
Bug Blocks: | 22160 |
Description
Chris Cormack
2010-05-21 01:24:44 UTC
Liz, could you take a look at this and see if it's still valid? Still valid? Pretty sure this is still valid... ModItemTransfer just obliterates any existing transfer and replaces it. I have done tests with 2 different use cases: * Item from A is checked out to user in B * Hold is placed with pickup in C * Items return home * Item is checked in at B * Transfer is to library C for hold pickup Similar as above, but the item is not checked out, when returned in B: * Transfer is to library C for hold pickup And then to verify that the holds behavior took precedence: * Item from A (without holds) is checked in at B * Item is sent to return to A I assume that this is fixed, please reopen if I missed something! |