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

[Bug 41467] New: When transfer not allowed the 'Originating branch' is not populated
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '26

13 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41467 Bug ID: 41467 Summary: When transfer not allowed the 'Originating branch' is not populated Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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(a)bywatersolutions.com To recreate: 1 - SET syspref UseBranchTransferLimits/BranchTransferLimitsType To Enfore based on collection 2 - Administration->Library Transfer limits click (Advanced editor) 3 - Uncheck Centerville->Fairfield for 'Fiction' 4 - Find or create a Fiction item at centerville 5 - Circulation->Transfer 6 - Attempt to transfer item to Fairfield 7 - Note 'Originating library' is blank -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 41435] New: Use template plugin with built in caching for authorised value conversions in search results
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '26

13 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41435 Bug ID: 41435 Summary: Use template plugin with built in caching for authorised value conversions in search results Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some values in search results use: AuthorisedValues.GetDescriptionByKohaField Some are looked up in the script For consistency and readability we should be consistent -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 41713] New: warnings sometimes generated when using ShowComponentRecords feature
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '26

13 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41713 Bug ID: 41713 Summary: warnings sometimes generated when using ShowComponentRecords feature Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When using ShowComponentRecords feature warnings like: [WARN] Use of uninitialized value in concatenation (.) or string at /kohadevbox/koha/Koha/SearchEngine/Elasticsearch/QueryBuilder.pm line 352. [WARN] Use of uninitialized value $comp_query_str in concatenation (.) or string at /kohadevbox/koha/catalogue/detail.pl line 273. are generated from staff interface detail view when: 1. ShowComponentRecords = 'both' or 'staff' AND 2. UseControlNumber is on AND 3. record lacks 001 field Similarly, from OPAC interface: [WARN] Use of uninitialized value in concatenation (.) or string at /kohadevbox/koha/Koha/SearchEngine/Elasticsearch/QueryBuilder.pm line 352. [WARN] Use of uninitialized value $comp_query_str in concatenation (.) or string at /kohadevbox/koha/opac/opac-detail.pl line 640. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 34710] New: Remove GreyBox from OPAC
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '26

13 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34710 Bug ID: 34710 Summary: Remove GreyBox from OPAC 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org When I grep for "greybox" in the OPAC, I only really see one two relevant references: koha-tmpl/opac-tmpl/bootstrap/en/includes/greybox.inc koha-tmpl/opac-tmpl/bootstrap/en/modules/opac-detail.tt The "opac-detail.tt" is just including "greybox.inc" I don't know enough about greybox to know how to remove it but it looks like it should be easy enough? -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 41094] New: search_anonymize_candidates returns too many candidates when FailedLoginAttempts is empty
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '26

13 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41094 Bug ID: 41094 Summary: search_anonymize_candidates returns too many candidates when FailedLoginAttempts is empty Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com >From a discussion on Mattermost with David Little. The arguable lines are: my $fails = C4::Context->preference('FailedLoginAttempts') || 0; $cond->{login_attempts} = [ -and => { '!=' => undef }, { -not_in => [ 0, 1 .. $fails - 1 ] } ]; -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 29393] New: Ability to send emails from patron details page
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '26

13 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29393 Bug ID: 29393 Summary: Ability to send emails from patron details page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 116

[Bug 40934] New: process_message_queue.pl add ability to exclude some letter code
by bugzilla-daemon＠bugs.koha-community.org 12 Mar '26

12 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40934 Bug ID: 40934 Summary: process_message_queue.pl add ability to exclude some letter code Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz It would help to add an argument to process_message_queue.pl to exclude some letter-code (like a blacklist, send all letter-code except these ones) Use case : Some library would like to send digest once per day (say at 20:05) but all others message every hour. It is currently possible to do that by having 2 lines process_message_queue.pl that way : ``` 00 */1 * * * process_message_queue.pl --code ACQ_NOTIF_ON_RECEIV --code CART ... # list all message except digest 05 20 * * * process_message_queue.pl #send all message including digest ``` The problem with this method is that we have to list almost all letter-code in the first line (around 85), there is a high chance that we forget some notification in the every hour line (thus these notifications will not be sent every hour as wanted) It would be great to be able to do it by excluding some letter code example: ``` 00 */1 * * * process_message_queue.pl --xcode DUEDGST --xcode PREDUEDGST --xcode HOLDDGST --xcode AUTO_RENEWALS_DGST # send all exepct digest 05 20 * * * process_message_queue.pl # send all including digest ``` (In this example, argument is xcode for exclude code but I'm not sure about the name) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 41514] New: The API should fully respect lead and trail periods for bookings
by bugzilla-daemon＠bugs.koha-community.org 12 Mar '26

12 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41514 Bug ID: 41514 Summary: The API should fully respect lead and trail periods for bookings Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Depends on: 37707 Currently, the lead/trail period handling for bookings is entirely handled in the UI. We should add handling to the API to ensure these settings are adhered to by third-party consumers too. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37707 [Bug 37707] Lead/Trail times should work in combination -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 41734] New: Need way to clear mandatory patron attributes once patron is no longer in a category using that attribute
by bugzilla-daemon＠bugs.koha-community.org 12 Mar '26

12 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41734 Bug ID: 41734 Summary: Need way to clear mandatory patron attributes once patron is no longer in a category using that attribute Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Scenario: library uses a reciprocal borrowing patron category and wants to track what neighboring area patrons are coming from, attribute is limited to patron category and mandatory. Patron moves, updates membership to be no longer reciprocal. The attribute cannot be removed while the patron is in a category using it, and the option disappears from the edit form once their new category no longer uses that attribute, but the data is left behind. A workaround is to blank that out with the batch patron modification tool, but it would be nice if, when moving a patron out of a category with a mandatory attribute, Koha offered a prompt to remove the no-longer-applicable attribute data. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 26603] New: Add the ability to have Patron driven choice in what format they receive messages
by bugzilla-daemon＠bugs.koha-community.org 12 Mar '26

12 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26603 Bug ID: 26603 Summary: Add the ability to have Patron driven choice in what format they receive messages Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, specifically to Overdues, it is up the library to decide how they send out their Overdue Notices- email, SMS, phone, print. It would be extremely helpful to libraries and patrons to have the patron choose which format they receive their message in - instead of the library sending it to all formats and for those patrons that have both SMS and email on file, they would only get this message in their desired format instead of both. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5