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

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

[Bug 42645] New: ModSuggestion: FallbackToSMSIfNoEmail ignores EmailFieldPrimary/EmailFieldPrecedence
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42645 Bug ID: 42645 Summary: ModSuggestion: FallbackToSMSIfNoEmail ignores EmailFieldPrimary/EmailFieldPrecedence Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org The transport-selection logic in C4/Suggestions.pm (ModSuggestion, ~line 253) checks !$patron->email when deciding whether to fall back to SMS for purchase-suggestion status-change notices (ACCEPTED, AVAILABLE, REJECTED, ORDERED, CHECKED). $patron->email returns the raw borrowers.email column value and does not consult the EmailFieldPrimary or EmailFieldPrecedence system preferences. The correct method is $patron->notice_email_address, which applies those preferences. A patron who has only emailpro or B_email populated (with borrowers.email empty) will incorrectly receive their status-change notice via SMS even when they have a valid, reachable email address, because the FallbackToSMSIfNoEmail check sees an empty borrowers.email and treats the patron as having no email at all. See also: Bug 39984 Test plan: 1. Enable FallbackToSMSIfNoEmail. 2. Set EmailFieldPrimary to emailpro (or EmailFieldPrecedence to emailpro|email|B_email). 3. Create a patron with emailpro populated, borrowers.email empty, and smsalertnumber set. 4. Submit a purchase suggestion as that patron and accept it. 5. Check the message_queue table. 6. Without patch: the ACCEPTED notice is queued with message_transport_type = 'sms'. 7. Apply patch: the ACCEPTED notice is queued with message_transport_type = 'email' and sent to the emailpro address. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 40945] New: "Aborted connection" warnings in tests output
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40945 Bug ID: 40945 Summary: "Aborted connection" warnings in tests output Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 25790 in a full console log of Jenkins you can see several tests raising this output: [Warning] Aborted connection 42 to db: 'koha_kohadev' user: 'koha_kohadev' host: '172.19.0.6' (Got an error reading communication packets) Those logs come from the db container. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25790 [Bug 25790] [OMNIBUS] warnings removal -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 40947] New: "Aborted connection 42 to db" from t/db_dependent/www/search_utf8.t
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40947 Bug ID: 40947 Summary: "Aborted connection 42 to db" from t/db_dependent/www/search_utf8.t Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 41682] New: Syspref discrepancies between new and upgraded installs
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41682 Bug ID: 41682 Summary: Syspref discrepancies between new and upgraded installs Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 49

[Bug 41709] New: GIR segment data should be encoded in EDI ORDERs
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '26

21 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41709 Bug ID: 41709 Summary: GIR segment data should be encoded in EDI ORDERs Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org We're properly escaping special characters from bib/item records in EDI Order messages, but we don't apply that escaping to any of the GIR contents which may well also include special characters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23