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

[Bug 39809] New: Category name and code in red and italic in patron category form
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39809 Bug ID: 39809 Summary: Category name and code in red and italic in patron category form Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org In main, when I go to the patron category form, the required fields' inputs are in red and italic. To recreate: A.1. Go to Administration > Patron categories A.2. Click New category --> Notice the labels for Category code, Description and Category type are in italic (they used to be just red and bold, but not italic) A.3. Type in a code and a description --> Notice that the input is now in red and italic (it used to be black and regular/not italic) B.1. Go to Administration > Patron categories B.2. Click on an existing category --> Notice the description inside the input field is in red and italic (it used to be black and regular/not italic) -- You are receiving this mail because: You are watching all bug changes.

1 26

[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 42441] New: Remove event attributes from authority merge template
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42441 Bug ID: 42441 Summary: Remove event attributes from authority merge template Initiative type: --- Sponsorship Sponsored 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 CC: testopia(a)bugs.koha-community.org Blocks: 38407 The authority merge template has a couple of "onClick" event attributes which should be moved to the JS block in the footer. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38407 [Bug 38407] Eliminate event handler attributes in the staff interface -- You are receiving this mail because: You are watching all bug changes.

1 26

[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 42359] New: t/db_dependent/Reports/Guided.t fails when ReportsLog is enabled
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '26

22 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42359 Bug ID: 42359 Summary: t/db_dependent/Reports/Guided.t fails when ReportsLog is enabled Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: nick(a)bywatersolutions.com Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When ReportsLog is enabled, one gets this failure on Koha main: t/db_dependent/Reports/Guided.t .. 8/14 # Failed test 'no warnings' # at /usr/share/perl/5.36/Test/Builder.pm line 193. # There were 1 warning(s) # Previous test 9 'Without id delete_report returns undef' # Use of uninitialized value in concatenation (.) or string at /kohadevbox/koha/C4/Reports/Guided.pm line 798. # at /kohadevbox/koha/C4/Reports/Guided.pm line 798. # C4::Reports::Guided::delete_report(1) called at t/db_dependent/Reports/Guided.t line 263 # main::__ANON__() called at /usr/share/perl/5.36/Test/Builder.pm line 374 # eval {...} called at /usr/share/perl/5.36/Test/Builder.pm line 374 # Test::Builder::subtest(Test::Builder=HASH(0xaaab107f82d0), "get_saved_reports", CODE(0xaaab1b732660)) called at /usr/share/perl/5.36/Test/More.pm line 809 # Test::More::subtest("get_saved_reports", CODE(0xaaab1b732660)) called at t/db_dependent/Reports/Guided.t line 325 # # Looks like you failed 1 test of 14. t/db_dependent/Reports/Guided.t .. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/14 subtests Test Summary Report ------------------- t/db_dependent/Reports/Guided.t (Wstat: 256 (exited 1) Tests: 14 Failed: 1) Failed test: 14 Non-zero exit status: 1 Files=1, Tests=14, 2 wallclock secs ( 0.01 usr 0.00 sys + 0.95 cusr 0.23 csys = 1.19 CPU) Result: FAIL -- You are receiving this mail because: You are watching all bug changes.

1 16