Bug 40486 - Item type not handled correctly when placing holds in staff interface
Summary: Item type not handled correctly when placing holds in staff interface
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-24 00:41 UTC by David Cook
Modified: 2025-07-24 00:42 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Cook 2025-07-24 00:41:52 UTC
When using the system preference "AllowHoldItemTypeSelection", you can specify the item type you want for "next available" holds.

Unfortunately, on /cgi-bin/koha/reserve/request.pl there is a "Request specific item type:" field at the top under "Hold details" and another under "Hold next available item".

Both of these fields get sent, which means that only the 1st one works. (To reproduce, enable that system preference and try to set the item type using the "Request specific item type:" under "Hold next available item". On the hold screen, "Books" won't appear in the "Details" column. Try again using the top field and this time you'll see under "Details" it says "Next available <itemtype> item".)

Also, it looks like this "itemtype" isn't passed to CanBookBeReserved. It just goes straight to AddReserve(). 

(See bug 40475 for more detail.)