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

[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 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

[Bug 43360] New: Wire the advanced search form to build Lucene queries via the new /search architecture (Bug 43355)
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43360 Bug ID: 43360 Summary: Wire the advanced search form to build Lucene queries via the new /search architecture (Bug 43355) Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Depends on: 43355 Target Milestone: --- Bug 43355 establishes a Lucene-style query language as Koha's standard search syntax. The staff and OPAC advanced search forms currently build queries in Koha's legacy internal parameter format (operators/operands/indexes arrays) - a second query representation to keep in sync alongside the new one. This bug updates the advanced search forms to build Lucene query strings behind the scenes and submit through the architecture Bug 43355 establishes, so there is one query language for Koha to maintain, not two, and advanced search benefits from the same query capabilities /search exposes to API consumers. Test plan: 1. To be written once Bug 43355 has landed and this bug's approach is scoped. This bug is part of a staged program building on Bug 43355; see that bug for the overall plan. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43355 [Bug 43355] Add a /search API endpoint for biblios -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 43358] New: Zebra: add a reduced-parity Lucene query translation layer for the new /search endpoint
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43358 Bug ID: 43358 Summary: Zebra: add a reduced-parity Lucene query translation layer for the new /search endpoint Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Depends on: 43355 Target Milestone: --- Bug 43355 establishes a Lucene-style query language as the standard syntax for the new /search endpoint, translated natively by Elasticsearch's own query_string handler. Zebra has no equivalent native support, and per community discussion on Bug 25870, cannot index items separately or join bibs/items the way the new architecture's item-level correctness (combined filters, facet accuracy, query-time OpacHiddenItems enforcement) depends on. This bug is deliberately scoped as reduced parity, not full feature parity: it adds a Lucene-to-PQF/CCL translation layer for basic syntax (field:value, AND/OR/NOT, quoted phrases, parentheses) so Zebra installations can use /search at all, while explicitly documenting that combined item-level filter correctness, facet accuracy against those filters, and query-time OpacHiddenItemsHidesRecord enforcement remain Elasticsearch-only, with Zebra falling back to today's existing (imperfect) behaviour for those specific concerns. This resolves the Bug 25870 disagreement between wanting Elasticsearch progress to not be blocked on Zebra parity, and not wanting Zebra abandoned outright. Test plan: 1. To be written once the parser design is finalised. This bug is part of a staged program building on Bug 43355; see that bug for the overall plan. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43355 [Bug 43355] Add a /search API endpoint for biblios -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 43357] New: api/v1/public/additional_contents gives 500 error if OPAC related entries lack non-required fields
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43357 Bug ID: 43357 Summary: api/v1/public/additional_contents gives 500 error if OPAC related entries lack non-required fields Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Target Milestone: --- To recreate: 1. Make an OPAC news or HTML customization entry 2. Leave one of the non-required fields empty (Expiration date and/or Appear in position ) 3. Visit {BASE_URL}/api/v1/public/additional_contents 4. 500 error Expected integer - got null. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 33712] New: Use new checkout api's for staff client checkouts
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33712 Bug ID: 33712 Summary: Use new checkout api's for staff client checkouts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, koha-bugs(a)lists.koha-community.org, tomascohen(a)gmail.com Depends on: 33709 Bug #23336 introduces some new checkout api's and then bug 33709 refines them a little. Once those are both pushed we should eat our own dogfood and consider updating the staff client workflows to use these API's instead of relying on the full page reloads we currently do. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33709 [Bug 33709] Add override options to checkouts endpoint(s) -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. You are watching all bug changes.

1 9

[Bug 23336] New: Add an API endpoint for issuing an item to a patron
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23336 Bug ID: 23336 Summary: Add an API endpoint for issuing an item to a patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com The Checkouts API route RFC (https://wiki.koha-community.org/wiki/Checkouts_endpoint_RFC) proposes a POST on /checkouts, which makes sense. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 108