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

[Bug 27113] New: ElasticSearch: Autocomplete in input search
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27113 Bug ID: 27113 Summary: ElasticSearch: Autocomplete in input search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: ivan.dziuba(a)inlibro.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 298

[Bug 25159] New: Action logs should be stored in JSON ( and as a diff of the change )
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25159 Bug ID: 25159 Summary: Action logs should be stored in JSON ( and as a diff of the change ) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Action logs would be much more readable if we changed the format from a raw Data::Dumper::Dumper string to JSON which we could format nicely in the interface. In addition, we could store changes to database rows ( and other data structures ) as a diff stored in JSON. I think the format from Struct::Diff::diff is nice. Given: my $x = { surname => 'Hall', firstname => 'Kyle', cardnumber => '12345', suffix => "Jr.", }; my $y = { surname => 'Hall', firstname => 'Kyle', cardnumber => '9876543', nickname => "K-dog" }; The diff looks like: { "D": { "cardnumber": { "N": "9876543" }, "nickname": { "A": "K-dog" }, "suffix": { "R": "Jr." } } } Where the D key is the difference, and indicates cardnumber has changed with an N, nickname has been added with an A, and suffix has been removed with an R. With this data we can easily construct a nice diff view ( perhaps green for added, red for removed, and yellow for changes showing the old and new value ). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 94

[Bug 36698] New: Display 'diff' nicely in action logs
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36698 Bug ID: 36698 Summary: Display 'diff' nicely in action logs Change sponsored?: --- Product: Koha Version: unspecified 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: 25159 We introduced a new 'diff' field in bug 25159.. it would be great to display a pretty diff using it. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25159 [Bug 25159] Action logs should be stored in JSON ( and as a diff of the change ) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 50

[Bug 39628] New: Display 'diff' satisfactorily in action logs
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39628 Bug ID: 39628 Summary: Display 'diff' satisfactorily in action logs Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: andrew(a)bywatersolutions.com Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 36698 Bug 36698 wants to display the diff nicely. As a stopgap, how about we just make it possible to display them as-is? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36698 [Bug 36698] Display 'diff' nicely in action logs -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 41132] New: variable 'branch' is not available in PASSWORD_RESET nor STAFF_PASSWORD_RESET
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41132 Bug ID: 41132 Summary: variable 'branch' is not available in PASSWORD_RESET nor STAFF_PASSWORD_RESET Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org The variable 'branch' (in TT) or 'branches' (in <<>>) is not available in notification PASSWORD_RESET and STAFF_PASSWORD_RESET. It would be useful to be able to display the library name or email (for example, in the signature(?) of the email). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 33116] New: Limit reports execution time with sql variables
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33116 Bug ID: 33116 Summary: Limit reports execution time with sql variables Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Users' SQL reports can run for a very long time and users can create cartesean products which severely impact server performance. Moreover it doesn't help there's a lot of sample koha reports using the old cartesean prone join synxtax. This patch add two optional koha-conf parameters: - report_sql_max_statement_time for mysql sql_max_statement_time - report_sql_max_join_size for sql_max_join_size -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 37598] New: Ability to use the BCC field for sending notices to multiple addresses, rather than the To field
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37598 Bug ID: 37598 Summary: Ability to use the BCC field for sending notices to multiple addresses, rather than the To field Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Bug 12802 allows libraries to select a list of email address fields to use when sending notices to patrons. You would check all of the email addresses you want to use in a new system preference EmailFieldSelection and Koha will send the notice to all of those addresses. However, all of those addresses do go through in the To field. They are not in the BCC field. It would be good to enable the option to use the BCC field for the email addresses rather than the To field. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 38940] New: ConsiderLibraryHoursInCirculation set to "shorten the loan period and set the checkout to be due at the library’s close time" does not appear to work
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38940 Bug ID: 38940 Summary: ConsiderLibraryHoursInCirculation set to "shorten the loan period and set the checkout to be due at the library’s close time" does not appear to work Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If I have ConsiderLibraryHoursInCirculation set to "shorten the loan period and set the checkout to be due at the library’s close time" and check out an item whose loan period should be shortened to account for closing hours, the loan period isn't being shortened as expected. To replicate: -Set ConsiderLibraryHoursInCirculation to "shorten the loan period and set the checkout to be due at the library’s close time" -Set Library A's hours from any opening time (I used 8a) to 12p -Set a circ rule for all patron types/test item type for hourly loans using the number of hours that would go past your closing time (test: 3 hours) -Check out the test item type at a time when the loan period should be shortened (test: 11.30a) -Note that the loan period is not shortened (test: 2.30p) despite the closing time and system preference -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 25796] New: Allow REST API to use external OAuth2 authorization server
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '26

30 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25796 Bug ID: 25796 Summary: Allow REST API to use external OAuth2 authorization server 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: dcook(a)prosentient.com.au At the moment, Koha's REST API only validates tokens using the embedded authorization server Net::OAuth2::AuthorizationServer. It would be great if Koha were configured to use an external authorization server (like Keycloak). We could redirect the /token endpoint to Keycloak, or just require consumers to query Keycloak directly for access tokens I suppose. Then we'd set up Koha to either embed (or more sustainably fetch) Keycloak's public key in order to verify that the access token is coming from Keycloak. We'd then do further token validation (to make sure it's not expired, it's for the correct audience, etc). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 40467] New: t/00-deprecated.t no longer needed
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40467 Bug ID: 40467 Summary: t/00-deprecated.t no longer needed Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement 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 it only tests for the presence of "switch" -- You are receiving this mail because: You are watching all bug changes.

1 16