Bug 26105 - Incorrect hold status shown if hold is ignored after transfer to pickup location
Summary: Incorrect hold status shown if hold is ignored after transfer to pickup location
Status: RESOLVED DUPLICATE of bug 26698
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-30 13:09 UTC by Andrew Fuerste-Henry
Modified: 2020-10-19 15:54 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2020-07-30 13:09:37 UTC
To recreate:
- Have an item at Branch A
- Place a hold for pickup at Branch B
- Check the item in at Branch A, confirm hold and transfer
- Confirm request.pl and detail.pl for your bib show item is in transit to Branch B
- Confirm circulation.pl and moremember.pl for your patron show item is in transit to Branch B
- Check item in at Branch B, click Ignore on the hold popup
- Detail.pl shows "There is an item level hold on this item (priority = 0)." -- the expected message for an item with an item-level hold with no Found value
- Request.pl shows priority of "In transit" and message of "Item waiting at Branch B since" with no waiting date
- Circulation.pl and moremember.pl show no priority or status for this hold
- the database shows found=T for this hold

To be honest, it's hard to think of a good reason why a library would ignore a hold at the end of its transfer, but this is still confusing and worth addressing.
Comment 1 Katrin Fischer 2020-10-19 15:46:48 UTC
Hi Andrew,

what is the expected behaviour? Should it be "" instead of T?

Adding Martin as he has been working on transfers.
Comment 2 Andrew Fuerste-Henry 2020-10-19 15:51:32 UTC

*** This bug has been marked as a duplicate of bug 26698 ***
Comment 3 Andrew Fuerste-Henry 2020-10-19 15:52:08 UTC
Looks like we re-discovered this one and patched it on bug 26698
Comment 4 Katrin Fischer 2020-10-19 15:54:03 UTC
Even better :)