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

[Bug 40276] New: Limit visibility of subscriptions based on library group
by bugzilla-daemon＠bugs.koha-community.org 05 Jan '26

05 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40276 Bug ID: 40276 Summary: Limit visibility of subscriptions based on library group 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org For large library systems making extensive use of both groups and serials, it would be helpful to have the option to limit subscription visibility based on group. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31102] New: Add granularity to serials to include permissions and visibility to subscriptions by branch
by bugzilla-daemon＠bugs.koha-community.org 05 Jan '26

05 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31102 Bug ID: 31102 Summary: Add granularity to serials to include permissions and visibility to subscriptions by branch Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice for larger consortiums to only see and use their own serials in the Serials Module. The ability for granularity with serial permissions to accommodate consortium, including the ability for each branch/library to limit visibility to own serials data would be nice. In Acquisitions, there is a way to limit the funds/budgets to a specific branch, it would be nice to do the same here in the Serials Module. In addition, add permissions to include only editing/checking in your own library's serials. Currently, the permission lives in Serials for when a library uses Independent Branches. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 35690] New: Searching patrons with contains does not provide relevant results
by bugzilla-daemon＠bugs.koha-community.org 05 Jan '26

05 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35690 Bug ID: 35690 Summary: Searching patrons with contains does not provide relevant results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Example: In this example the library has the PatronSearchMethod system preference set to 'contains'. They attempted to search for a patron named 'Don Smith' but the primary search results are showing names such as 'Brandon Smith' and patrons who are located at their 'Smith Public Library' such as 'Madonna Jones - Smith Public Library'. It would be ideal if the search results showed relevant patrons first before suggesting patrons located at their 'Smith Public Library'. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 41519] New: Cannot turn off automatic renewal for individual checkout if set in circulation rules
by bugzilla-daemon＠bugs.koha-community.org 05 Jan '26

05 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41519 Bug ID: 41519 Summary: Cannot turn off automatic renewal for individual checkout if set in circulation rules Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com If "Automatic renewal" is set to "Yes" in the circulation and fines rules, you cannot turn off "automatic renewal" at the issue level. This makes some sense because you don't know until after the checkout is done whether or not automatic renewal will be applied (unless you're ticking the checkbox "Automatic renewal" when doing the checkout). However, surely there must be some way of disabling automatic renewal for an issue? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 40775] New: Hide "The item is scheduled for auto renewal" in the OPAC when item is currently not renewable
by bugzilla-daemon＠bugs.koha-community.org 05 Jan '26

05 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40775 Bug ID: 40775 Summary: Hide "The item is scheduled for auto renewal" in the OPAC when item is currently not renewable Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bdaeuber(a)cityoffargo.com QA Contact: testopia(a)bugs.koha-community.org In the OPAC if an checkout is on hold, reached the maximum number of renewals, or has some other circumstance that would prevent renewal, there is still a "this item is schedule for auto renewal" message, which can be confusing to patrons. If the circ rules or a system preference would prevent the item from being renewed, it would be nice if we could hide that message until the circumstances change. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 39138] New: Extend uppercase formatting options beyond uppercasesurnames preference
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '26

03 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39138 Bug ID: 39138 Summary: Extend uppercase formatting options beyond uppercasesurnames preference Change sponsored?: --- 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.m.hall(a)gmail.com Libraries can turn on uppercasesurnames preference to force capitalization on patron last names, but some libraries would like to be able to do the same with other borrower fields. It would be nice if this could be a system preference allowing them to select borrower fields to format in uppercase. Could call it BorroweUppercaseField, and maybe uppercasesurnames could roll into that eventually. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 40339] New: Merge patrons causes guarantees without guarantors
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '26

03 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40339 Bug ID: 40339 Summary: Merge patrons causes guarantees without guarantors Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: mikko.liimatainen(a)turku.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When merging patrons, guarantees aren't transferred to the patron that is kept. This causes guarantees without a guarantor. Merging should check for guarantees and transfer them to the kept guarantor. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 41515] New: Ability to exclude a facet value in OPAC search results
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '26

03 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41515 Bug ID: 41515 Summary: Ability to exclude a facet value in OPAC search results Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It could be useful for some searches. My discovery tool gives our patrons this ability, but not Koha's OPAC. Same idea here but for staff interface : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27678 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 32577] New: Transactions table overflows window-size
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '26

03 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32577 Bug ID: 32577 Summary: Transactions table overflows window-size Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 145090 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=145090&action=e… Image of issue When a transaction is added to a patron's account the table overflows the div and is cut-off by the window size. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 34816] New: Elasticsearch needs the ability to map the index according to the MARC field indicator
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '26

03 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34816 Bug ID: 34816 Summary: Elasticsearch needs the ability to map the index according to the MARC field indicator Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: anneli.osterman(a)koha-suomi.fi Elasticsearch needs the ability to map the index according to the MARC field indicator. For example, the value of the 2nd indicator of field 264 defines whether it is a publisher, manufacturer or distributor. These operators should be able to map to different indexes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4