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

[Bug 38728] New: Add option to automatically trigger cashup summary modal after cashup
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38728 Bug ID: 38728 Summary: Add option to automatically trigger cashup summary modal after cashup 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 13985 I actually thought this was already the case... the cashup summary that can be displayed for cashups appearing immediately after a cashup so you can print the transactions. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13985 [Bug 13985] [Omnibus] Cash Management - Koha as 'Point of Sale' -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 38

[Bug 38061] New: Serials collection table improvements
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38061 Bug ID: 38061 Summary: Serials collection table improvements Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)ptfs-europe.com 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 67

[Bug 37538] New: Improve documentation of connexion_import_daemon.pl
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37538 Bug ID: 37538 Summary: Improve documentation of connexion_import_daemon.pl Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: rudolfbyker(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Patch incoming :) See related discussions at: - https://chat.koha-community.org/koha-community/pl/o18q57a1pt879dgp63ujtcajpe - https://chat.koha-community.org/koha-community/pl/gz3mjusns3bdme3j4f8sp83sfw - https://chat.koha-community.org/koha-community/pl/yzxmrfegcbnrjgqgjt7t6wjwhy I plan to follow this up with a patch for the koha-manual, which I will also link here. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 37099] New: Add uniform title fields to the title and subject Elasticsearch index mappings
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37099 Bug ID: 37099 Summary: Add uniform title fields to the title and subject Elasticsearch index mappings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz We would like: A 'title' or 'title as phrase' search to also search on the following Uniform Title fields: * 130$a * 240$a * 730$a A 'subject' or 'subject as phrase' search to also search on the following Uniform Title fields: * 630$a -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 36849] New: Add more tags to Elasticsearch mapping for title, title as phrase
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36849 Bug ID: 36849 Summary: Add more tags to Elasticsearch mapping for title, title as phrase Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz Libraries may expect a 'title' search to look at a few other tags that aren't currently mapped. To the title index for MARC21, we would like to additionally map: * 440a * 600t * 800t * 810t * 830np -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 35192] New: Highlight search terms in OPAC Title notes tab
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35192 Bug ID: 35192 Summary: Highlight search terms in OPAC Title notes tab Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org It would be nice if Koha could highlight the search term in the title notes tab of a OPAC biblio detail page. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 32736] New: koha-worker should be able to restart all queues with a single call
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32736 Bug ID: 32736 Summary: koha-worker should be able to restart all queues with a single call Change sponsored?: --- Product: Koha Version: master 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 Maybe a --queue all or something? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 41540] New: staffShibOnly - update description for system preference
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '26

15 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41540 Bug ID: 41540 Summary: staffShibOnly - update description for system preference Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The description is currently: [Allow|Don't allow] staff to login by means other than shibboleth. Two minor fixes: 1. "login" to "log in" 2. "shibboleth" to "Shibboleth" (capitalise, as it is a proper name) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 41710] New: SearchEngine/Elasticsearch/Search.t does not rollback properly
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '26

14 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41710 Bug ID: 41710 Summary: SearchEngine/Elasticsearch/Search.t does not rollback properly Initiative type: --- Sponsorship --- status: 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 syspref ElasticsearchIndexStatus_mydb is created in DB and persists after the tests finished. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 41315] New: Using patron-homelibrary option for overdue notices may not send notices to all branches
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '26

14 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41315 Bug ID: 41315 Summary: Using patron-homelibrary option for overdue notices may not send notices to all branches Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Bug 32740 added the option to send overdue notices from the patron's homelibrary. The branchcode variable is used for several purposes, in the new code: 649 if ($patron_homelibrary) { 650 $branchcode = $patron->branchcode; 651 $library = Koha::Libraries->find($branchcode); 652 $admin_email_address = $library->from_email_address; 653 $branch_email_address = C4::Context->preference('AddressForFailedOverdueNotices') 654 || $library->inbound_email_address; 655 } We change that branchcode param based on the patron, however, earlier when getting the list of patrons we limit by issue branch: 567 my $borrower_sql = <<"END_SQL"; 568 SELECT issues.borrowernumber, firstname, surname, address, address2, city, zipcode, country, email, emailpro, B_email, smsalertnumber, phone, cardnumber, date_due 569 FROM issues,borrowers,categories,items 570 WHERE issues.borrowernumber=borrowers.borrowernumber 571 AND borrowers.categorycode=categories.categorycode 572 AND issues.itemnumber = items.itemnumber 573 AND items.itemlost = 0 574 AND TO_DAYS($date)-TO_DAYS(issues.date_due) >= 0 575 END_SQL 576 my @borrower_parameters; 577 if ($branchcode) { 578 if ($owning_library) { 579 $borrower_sql .= ' AND items.homebranch=? '; 580 } else { 581 $borrower_sql .= ' AND issues.branchcode=? '; 582 } 583 push @borrower_parameters, $branchcode; 584 } So we may have a patron from a different branch when we go through here, and end up changing the branch we will look at during the next pass of the code above I recreated by checking out three items to patrons from different branches, 1 day overdue each: MariaDB [koha_kohadev]> SELECT borrowers.cardnumber, borrowers.surname, borrowers.branchcode, borrowers.categorycode, issues.issue_id, issues.branchcode, issues.date_due FROM issues JOIN borrowers USING (borrowernumber); +----------------+---------+------------+--------------+----------+------------+---------------------+ | cardnumber | surname | branchcode | categorycode | issue_id | branchcode | date_due | +----------------+---------+------------+--------------+----------+------------+---------------------+ | 23529001000463 | Acosta | MPL | PT | 1 | CPL | 2025-11-25 23:59:00 | | 23529000139858 | Ballard | FFL | PT | 2 | CPL | 2025-11-25 23:59:00 | | 23529000035676 | Acevedo | IPT | PT | 3 | CPL | 2025-11-25 23:59:00 | +----------------+---------+------------+--------------+----------+------------+---------------------+ 3 rows in set (0.001 sec) Setting overdue rules to trigger at 1 day, then got this output: branch 'CPL', categorycode = PT pass 1 Using letter code 'ODUE' for pass 1 Found 3 borrowers with overdues borrower Acosta, Edna (5) has items triggering level 1. borrower Acevedo, Henry (19) has items triggering level 1. borrower Ballard, Ronnie (21) has items triggering level 1. branch 'FFL', categorycode = PT pass 2 No letter code found for pass 2 branch 'FFL', categorycode = PT pass 3 No letter code found for pass 3 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27