July 2025 - Koha-bugs - lists.koha-community.org

[Bug 40486] New: Item type not handled correctly when placing holds in staff interface
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40486 Bug ID: 40486 Summary: Item type not handled correctly when placing holds in staff interface Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com 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.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 40475] New: Item type not considered for next available hold in OPAC
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '25

24 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40475 Bug ID: 40475 Summary: Item type not considered for next available hold in OPAC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com I was discussing CanBookBeReserved with Pedro on bug 15516 when I noticed that the $itemtype in the following line of opac/opac-reserve.pl looks like it'll always be "undef" for "next available" holds: my $status = CanBookBeReserved( $borrowernumber, $biblioNum, $branch, { itemtype => $itemtype } )->{status}; -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 32135] New: Ability to batch cancel transfers
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32135 Bug ID: 32135 Summary: Ability to batch cancel transfers Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: madamyk(a)ckls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com For consortiums and other large systems, it would be helpful to have the ability to batch cancel transfers, or cancel more than one at a time. Most likely the easiest place to do this would be on the Transfers to Receive page, where you might be able to add a "Cancel Transfer" checkbox instead of (or in addition to) the button. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 37193] New: We could perhaps promote the community and it's tools more from inside Koha
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37193 Bug ID: 37193 Summary: We could perhaps promote the community and it's tools more from inside Koha Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It occurred to me today that other than linking out to the manual.. we don't really promote the community from Koha itself. I can't see any link to koha-community.org, chat.koha-community.org, bugs.koha-community.org or dashboard.koha-community.org anywhere. Perhaps we could add some to the about area to encourage more engagement with the community projects? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 11962] New 'cluster' install mode
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11962 Martin Renvoize (ashimema) <martin.renvoize(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |LATER Status|NEW |RESOLVED CC| |martin.renvoize(a)openfifth.c | |o.uk -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 26625] New: Add a mojolicious section in $KOHA_CONF
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26625 Bug ID: 26625 Summary: Add a mojolicious section in $KOHA_CONF Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 20582 This will allow to configure hypnotoad (and probably other things too in the future) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20582 [Bug 20582] Turn Koha into a Mojolicious application -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 32423] New: Allow guarantor to renew guarantee's checkouts
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32423 Bug ID: 32423 Summary: Allow guarantor to renew guarantee's checkouts Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org >From bug 3591 Right now, if AllowStaffToSetCheckoutsVisibilityForGuarantor or AllowPatronToSetCheckoutsVisibilityForGuarantor is set and the patron has consented to show their checkouts to their guarantor, the guarantor can see their guarantee's checkouts when logging into their own account in the OPAC. However, if they want to renew their guarantee's checkouts, they must log out and log in as their guarantee (or nag them if they don't have access). It would be great if the guarantor could renew from their own account. It could be the same as AllowStaff/PatronToSetCheckoutsVisibilityForGuarantor in the sense that the guarantee would have to "agree" to it to preserve confidentiality for older guarantees. (The use case I'm seeing the most is a family with small children, where the parent could renew all their family's checkouts from their own account.) -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 39348] New: Supplementary fields order in tables should be manageable
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39348 Bug ID: 39348 Summary: Supplementary fields order in tables should be manageable Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If a supplementary field is created with the "searchable" option it is displayed in the appropriate table, but there is no way to define its position in the table. It should be useful for improving usabilty of tables. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 34495] New: AutomaticConfirmTransfer does not confirm if the check-in form is resubmitted
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34495 Bug ID: 34495 Summary: AutomaticConfirmTransfer does not confirm if the check-in form is resubmitted Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 33300 Bug 29792 added a new system preference, AutomaticConfirmTransfer, to control the behavior of a transfer when the user clicked away from the "Wrong Transfer" modal without selecting anything. (assuming TransfersBlockCirc is set to "Don't block") With the syspref set to automatically confirm, it works as intended if the user literally clicks away from the modal using the mouse. However, if the user submits the check-in form again without selecting an option on the modal (i.e. by scanning the next item, or accidentally double-scanning the item initiating the transfer), then the transfer is not confirmed. It looks like this is happening because the automatic confirmation is triggered when the modal is hidden by Bootstrap event. If the check-in form is resubmitted, it doesn't actively hide the modal before reloading the page, so the automatic confirmation is not triggered. To reproduce: 0. Configure sysprefs and circulation rules: a. TransfersBlockCirc to Don't block b. AutomaticConfirmTransfer to Do c. In the circulation rules, set the default return policy to "Item returns home" 1. Find an item that belongs to a different library and check it in 2. When the transfer modal appears, click away from the modal. -> Notice the animation - the modal appears to fade upwards. 3. Query the transfer table -> Notice that there is a transfer with values for daterequested and datesent 4. Check the item in again 5. When the Wrong Transfer modal appears, click away from the modal. -> Notice the animation - the modal appears to fade upwards. 6. Query the transfer table -> Notice that the previous transfer was canceled, and there is a new transfer with values for daterequested and datesent 7. Repeat steps 1-6, except instead of clicking away from the modals, press Enter on the keyboard instead -> Notice that the animation no longer appears - the modals simply disappear when the page is reloaded -> Notice that after the Wrong Transfer modal is bypassed like this, the transfer table shows that the previous transfer was canceled, and there is a new transfer with a value for daterequested but no value for datesent Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33300 [Bug 33300] Wrong system preference name AutomaticWrongTransfer -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 37035] New: Merging authorities triggers rebuilding holds for all affected records when RealTimeHoldsQueue is enabled
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '25

23 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37035 Bug ID: 37035 Summary: Merging authorities triggers rebuilding holds for all affected records when RealTimeHoldsQueue is enabled Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If RealTimeHoldsQueue is on, merging authorities triggers a update_holds_queue_for_biblios background job for each affected record. This can result in thousands of unnecessary queued jobs since this change will not affect hold-ability. In a large catalog this can be a crippling number of background jobs that will delay more important jobs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14