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

[Bug 41386] New: Adding 0.00 as value for "Expired hold charge" in circulation rules can lead to exception Koha::Exceptions::Account::AmountNotPositive
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41386 Bug ID: 41386 Summary: Adding 0.00 as value for "Expired hold charge" in circulation rules can lead to exception Koha::Exceptions::Account::AmountNotPositive Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org If one adds 0.00 as "Expired hold charge" rules value in circulation rules and charge is then tried to add to a patron via Koha::Account->add_debit, exception Koha::Exceptions::Account::AmountNotPositive is raised. This can be really confusing for the users since monetary values in circulation rules typically allow using decimal values in them. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 41124] New: Add search options for moving hold to new biblio record
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41124 Bug ID: 41124 Summary: Add search options for moving hold to new biblio record Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Depends on: 31698 Currently moving a hold to a new biblio record requires the user to enter the biblionumber of the new record. It would be helpful if a search for the new target bib could be incorporated into the workflow to move the hold. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31698 [Bug 31698] Add ability to move a hold to a new bibliographic record/item -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 19557] New: Saved Filters from Advanced Search in OPAC
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19557 Bug ID: 19557 Summary: Saved Filters from Advanced Search in OPAC 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: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If a patron performs an advanced search on the OPAC, the filters (that they selected on the advanced search page) will not save if the patron searches then edits the search box on the results page. Steps 1) Click on the advanced search link 2) Search for keyword or title in your collection 3) Your brief results page populates 4) This will give you a breadcrumb trail of your advanced search (RESULTS OF SEARCH FOR 'KW,WRDL: FLORIDA NOT KW,WRDL: TRAVEL' 5) select a facet on the left to filter your results 6) now search in the search box on cgi-bin/koha/opac-search.pl While Koha treats this as a new search, it would be great to have an option for the patron to modify that original advanced search -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 20481] New: Subscriptions with multiple late issues do not properly convert to makePreviousSerialAvailable status when the late issues are brought in
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20481 Bug ID: 20481 Summary: Subscriptions with multiple late issues do not properly convert to makePreviousSerialAvailable status when the late issues are brought in Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When a library is using the system preference makePreviousSerialAvailable it allows them to make a previous serial automatically available when receiving a new serial issue. However if there are multiple serials marked late in the subscription, the system preference makePreviousSerialAvailable does not automatically change when the next item is brought in. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 39199] New: REST API: Add POST route for updating notices/message queue
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39199 Bug ID: 39199 Summary: REST API: Add POST route for updating notices/message queue Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement 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 It would be nice to have an 'addNotice' route. This would be useful for libraries that use a 3rd party for sending notices so that those sent notices could be included in the patron notice tab. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 42154] New: Bug 38714 hid the "New match check" link in record matching rules
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42154 Bug ID: 42154 Summary: Bug 38714 hid the "New match check" link in record matching rules Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 38714 In a follow-up on Bug 38714 I made an incorrect change to the logic for displaying the "New match check" link. It should check for matchchecks, not matchpoints. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38714 [Bug 38714] Adjust templates for prettier -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 41999] New: Suggestions table in staff interface no longer searches all data following title in Suggestion column
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41999 Bug ID: 41999 Summary: Suggestions table in staff interface no longer searches all data following title in Suggestion column Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Keywords: regression Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 33430 In 24.11, prior to the changeover to API in Bug 33430, the search box at the top of the Suggestions table in the staff interface was able to search all of the data in the Suggestion column. This includes data points like author, isbn, publisher, and publication year that are all very useful. Currently in main, the search box only looks at title in this column. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33430 [Bug 33430] Use REST API for suggestions tables -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 17258] New: [OMIBUS] MySQL 5.7
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17258 Bug ID: 17258 Summary: [OMIBUS] MySQL 5.7 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org This is an omnibus report to group the different issues under MySQL 5.7 -- You are receiving this mail because: You are watching all bug changes.

1 137

[Bug 21941] New: Incorrect GROUP BY in circ/reserveratios.pl
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21941 Bug ID: 21941 Summary: Incorrect GROUP BY in circ/reserveratios.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com DBD::mysql::st execute failed: 'koha_kohadev.reserves.reservedate' isn't in GROUP BY [for Statement "SELECT reservedate, reserves.borrowernumber as borrowernumber, reserves.biblionumber, reserves.branchcode as branch, items.holdingbranch, items.itemcallnumber, items.itemnumber, GROUP_CONCAT(DISTINCT items.itemcallnumber ORDER BY items.itemnumber SEPARATOR '|') as listcall, GROUP_CONCAT(DISTINCT homebranch ORDER BY items.itemnumber SEPARATOR '|') as homebranch_list, GROUP_CONCAT(DISTINCT holdingbranch ORDER BY items.itemnumber SEPARATOR '|') as holdingbranch_list, GROUP_CONCAT(DISTINCT items.location ORDER BY items.itemnumber SEPARATOR '|') as l_location, GROUP_CONCAT(DISTINCT items.itype ORDER BY items.itemnumber SEPARATOR '|') as l_itype, reserves.found, biblio.title, biblio.author, count(DISTINCT reserves.borrowernumber) as reservecount, count(DISTINCT items.itemnumber) as itemcount FROM reserves LEFT JOIN items ON items.biblionumber=reserves.biblionumber LEFT JOIN biblio ON reserves.biblionumber=biblio.biblionumber WHERE notforloan = 0 AND damaged = 0 AND itemlost = 0 AND withdrawn = 0 AND reservedate >= ? AND reservedate <= ? GROUP BY reserves.biblionumber ORDER BY reservecount DESC" with ParamValues: 0='2017-12-04 00:00', 1='2018-12-04 00:00'] at /home/vagrant/kohaclone/circ/reserveratios.pl line 150. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 41292] New: Add "force_password_reset_when_set_by_staff" to column name whitelist
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41292 Bug ID: 41292 Summary: Add "force_password_reset_when_set_by_staff" to column name whitelist Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com Bug 37508 added filters to Koha SQL reports and prevents them from using column names containing sensitive information. It also created a whitelist of non-sensitive columns that are accidentally blocked by that same filter. Bug 33462 added categories.force_password_reset_when_set_by_staff as a new column in the database. categories.force_password_reset_when_set_by_staff contains no sensitive data but is still blocked by the filters created in Bug 37508. categories.force_password_reset_when_set_by_staff should be added to the whitelist. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23