Summary: | Bookings place on 'any item' always use the first item | ||
---|---|---|---|
Product: | Koha | Reporter: | Nick Clemens (kidclamp) <nick> |
Component: | Architecture, internals, and plumbing | Assignee: | Martin Renvoize (ashimema) <martin.renvoize> |
Status: | RESOLVED DUPLICATE | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | data-27FC05A3CB97, lisette, marie.hedbom |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | Bookings | |
Bug Depends on: | 29002 | ||
Bug Blocks: |
Description
Nick Clemens (kidclamp)
2024-03-06 14:45:15 UTC
It seems that setting the item_id value of the booking (in the bookings) table causes the particular booking to be record level. So far it looks like everything still behaves correctly in terms of avoiding conflicting or overlapping bookings. So possibly all that's needed might be to simply not set item_id when 'any item' is selected. (In reply to jpl from comment #1) > It seems that setting the item_id value of the booking (in the bookings) > table causes the particular booking to be record level. So far it looks like > everything still behaves correctly in terms of avoiding conflicting or > overlapping bookings. > > So possibly all that's needed might be to simply not set item_id when 'any > item' is selected. Correction: setting item_id to NULL causes a record level booking. The intention was to allow record-level bookings, but the picker logic can't currently handle that so I added the auto-assignment at booking time as a workaround. We fix the randomisation of item selection in bug 38175 also.. where I add unit tests for the assignment function. *** This bug has been marked as a duplicate of bug 38175 *** |