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

[Bug 43351] New: Dynamic Transport Cost Matrix
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '26

22 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43351 Bug ID: 43351 Summary: Dynamic Transport Cost Matrix Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- The Transport Cost Matrix in a fantastic help at making the hold system more balanced and fair. However, setup and maintenance can be very daunting for those system that have MANY branches (Think 28 or even 70 branches!). What would be fantastic to see is a set of parameters that are setup under each branch - geolocation, hours, days open, zones, number of couriers. Some of this might already be defined through calendars or the hours that show on the opac. Then we could have options for quick setup, and ongoing adjustments if anything changes over time. Have options in the TCM to set automatically calculated values based on any combination of the above criteria, plus collection counts from each branch. For us, geolocation alone would be helpful in calculating distances between branches. I know that some people avoid the TCM because of the overwhelming task of initial setup, or even figuring out what to base calculations on. This would be a huge improvement to a powerful tool, making it more user friendly. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 41660] New: Action logs are not created for automatic item updates triggered by UpdateNotForLoanStatusOnCheckin / UpdateNotForLoanStatusOnCheckout
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '26

22 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41660 Bug ID: 41660 Summary: Action logs are not created for automatic item updates triggered by UpdateNotForLoanStatusOnCheckin / UpdateNotForLoanStatusOnCheckout Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: elina.uotila(a)jarvenpaa.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When an item’s not for loan status is automatically updated by the system preference UpdateNotForLoanStatusOnCheckin or by the system preference UpdateNotForLoanStatusOnCheckout, no entry is written to the action_logs table. In contrast, manually updating an item’s not for loan status does create an entry in action_logs when CataloguingLog is set to Log. Automatic updates triggered by these system preferences should also be recorded in action_logs for consistency and auditability. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 39386] New: UpdateNotForLoanStatusOnCheckin and UpdateNotForLoanStatusOnCheckout do not work
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '26

22 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39386 Bug ID: 39386 Summary: UpdateNotForLoanStatusOnCheckin and UpdateNotForLoanStatusOnCheckout do not work Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: stephanie.etallaz(a)univ-cotedazur.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Test plan: 1 - Set UpdateNotForLoanStatusOnCheckin to 2: 0 2 - Set UpdateNotForLoanStatusOnCheckout to _ALL_: 0: 2 3 - Check out a book -> Its notforloan status isn't set to 2 4 - Check in the book -> Its notforloan status isn't set to 0 and you don't get a notification -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 41238] New: Pseudonymize statistic jobs don't update progress
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41238 Bug ID: 41238 Summary: Pseudonymize statistic jobs don't update progress Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To test: Enable pseudonymization, may need to add bcrypt settings (see bug 28911) Perform some circulations View the jobs (Admin->Manage jobs) Filter for Pseudonymize statistic Note the progress is 0/1 even when job finished -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 38345] New: Remove support for OpenSearch
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38345 Bug ID: 38345 Summary: Remove support for OpenSearch Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Truth is our test suite has been exploding consistently when trying to launch OpenSearch: * https://jenkins.koha-community.org/job/Koha_Main_OS2/ * https://jenkins.koha-community.org/job/Koha_Main_OS1/ This has some precedent discussion on [issue 429](https://gitlab.com/koha-community/koha-testing-docker/-/issues/429) in `KTD` project issues. We are not going to remove it, I guess. But some noise is needed as people using OpenSearch in production don't seem to care we are not being able to run the test suite, so probably promising some 'OpenSearch support' that we cannot guarantee in any way. And if there's a problem with OpenSearch, we (devs) cannot launch a working environment to fix/test. My two cents on this matter. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 70

[Bug 40980] New: Clicking a search facet without logging in may trigger a cud-login error
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40980 Bug ID: 40980 Summary: Clicking a search facet without logging in may trigger a cud-login error Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 41408] New: POS Inline Editing Triggers Form Submission on Enter Key
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41408 Bug ID: 41408 Summary: POS Inline Editing Triggers Form Submission on Enter Key Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Point of Sale Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk On the Point of Sale (POS) page, when editing the cost of an item using inline table editing (clicking to edit the price), pressing Enter to accept the new price inadvertently submits the entire payment form instead of just accepting the inline edit. Steps to Reproduce 1. Navigate to the Point of Sale page (pos/pay.pl) 2. Add an item to "This sale" table using the '+Add' button from the left table 3. Click on the "Cost" cell to edit the price inline 4. Change the value 5. Press Enter to accept the new price Expected Behavior - The Enter key should accept the inline edit and update the cell value - The form should NOT be submitted - User should be able to continue editing other fields or adding more items Actual Behavior - The Enter key accepts the inline edit BUT also triggers the form submission - The payment form is submitted prematurely - User cannot continue with the transaction setup -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 41757] New: Copy default framework values to an ILL record
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41757 Bug ID: 41757 Summary: Copy default framework values to an ILL record Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com Default values of a framework used with ILL records will not get copied to the created record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 43021] New: A single malformed Z39.50/SRU result can break search and staged record preview
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43021 Bug ID: 43021 Summary: A single malformed Z39.50/SRU result can break search and staged record preview Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 35104 Target Milestone: --- Two related, unguarded MARC decode calls in the Z39.50/SRU search and staged record ("breeding") preview flow: 1. C4::Breeding::_handle_one_result (C4/Breeding.pm) calls MARC::Record->new_from_xml on each SRU search result with no eval. The caller loop that iterates search results across all configured servers already has per-result error handling for other kinds of failures (connection diagnostics collected in @errconn), but this call bypasses it entirely - one malformed record from any searched server aborts the whole results page for the cataloguer running the search. 2. MARCfindbreeding in cataloguing/addbiblio.pl calls MARC::Record->new_from_usmarc on a staged ("breeding") record with no eval, when a cataloguer opens that staged record to preview/import it. Both should catch a decode failure for the one affected record and report it to the user (e.g. skip that result with a visible message, or show a clear error instead of a blank/broken page) rather than propagating an uncaught exception. Found while auditing other places in the codebase that ingest externally-sourced MARC data, prompted by bug 35104. Test plan: 1. Configure a Z39.50/SRU target and search it for records, where at least one result server returns a record whose MARC cannot be decoded (or simulate by mocking C4::Breeding::_handle_one_result's input). 2. Before a fix: the whole results page fails/errors out. 3. Separately, stage a file containing an undecodable record via Stage MARC records for import, then open it via the cataloguing "breeding" preview. 4. Before a fix: the preview page errors out. 5. After a fix: both cases show a clear per-record error and let the user continue working with the rest of the results/batch. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35104 [Bug 35104] We should warn when attempting to save MARC records that contain characters invalid in XML -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 38368] New: Background jobs: Batch item record deletion to list failed/succeeded items
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38368 Bug ID: 38368 Summary: Background jobs: Batch item record deletion to list failed/succeeded items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: hanna.ikonen(a)sivistys.mikkeli.fi QA Contact: testopia(a)bugs.koha-community.org Currently background jobs do not list on visible record the items which have been handled. This causes issues especially when the background job fails, for example in batch item record deletion. Trying to solve which items have been worked with, you need to use several different reports. That means a lot of work hours, especially if, for example, the failed background job contains a lot of deleted items. My proposition is, that the background job -list would show which items were handled in the background whether it has failed or not. It would also be helpful if it showed information why it has failed/which item has caused the failure. It would standardize the information/notification system with the other batch processing jobs which list the things that have been worked on. To test: 1. Go to Administration and click Manage Jobs. 2. Select Status as "Failed" and Type "Batch item record deletion". 3. Open a failed background job. 4. Report only lists the job as failed, while "Detailed messages" is empty”. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6