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

[Bug 40035] New: Manual restrictions added in memberentry.pl without a note or date are not saved
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40035 Bug ID: 40035 Summary: Manual restrictions added in memberentry.pl without a note or date are not saved Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: philip.orr(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If you are currently editing a patron and in memberentry.pl you add a manual restriction by clicking on "Add manual restriction", but do not fill out the Comment or Expiration Date fields, the restriction will not be saved. To replicate: 1. Go to a patron account 2. Edit them 3. "Add manual restriction" 4. Leave it set to "Manual" type, no entry in note or date, save the patron 5. There won't be a restriction in their account. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 39105] New: List of accepted suggestions filtered with branch shows only suggestions without budget id
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39105 Bug ID: 39105 Summary: List of accepted suggestions filtered with branch shows only suggestions without budget id Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: minna.kivinen(a)hamk.fi QA Contact: testopia(a)bugs.koha-community.org When looking at the list of accepted suggestions, it shows all accepted suggestions for your branch. Byt when you change to branch to all or any other branch, the list shows only suggestions with no budgetid. Path: 1. Choose suggestions from aquisitions menu 2. Choose tab Accepted 3. Change branch to any other library or any. 4. On the list shows only suggestions with no Fund. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29490] New: Preview for more notices
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29490 Bug ID: 29490 Summary: Preview for more notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be great to have the preview option available on more notices.. currently, it's limited to CHECKIN, CHECKOUT and HOLD_SLIP. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 25795] New: Add OAuth2 scopes to REST API
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25795 Bug ID: 25795 Summary: Add OAuth2 scopes to REST API 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 It could be useful to add OAuth2 scopes for managing authorization for the REST API. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 20402] New: Implement OAuth2 authentication for REST API
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20402 Bug ID: 20402 Summary: Implement OAuth2 authentication for REST API Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: REST api Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com -- You are receiving this mail because: You are watching all bug changes.

1 94

[Bug 23204] New: Script for exporting Elasticsearch mappings to YAML
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23204 Bug ID: 23204 Summary: Script for exporting Elasticsearch mappings to YAML 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: alex.arnaud(a)biblibre.com Target Milestone: --- Sometimes we need to report librarian's mapping changes in DB to the mappings.yaml. This can be long and tedious. So, here is a script that do the job. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 70

[Bug 35138] New: Elastic search - add new facets
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35138 Bug ID: 35138 Summary: Elastic search - add new facets 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: michaela.sieber(a)kit.edu We would like to create a new facet for a 9xx-MARC field As Nick mentioned in Bug 18235, Comment 7: -labels shouldn't be hardcoded - staff should be able to set them -we should add more options to what can be faceted- could be out of control but technically any field should be able to be used -ES has better handling for faceting (can provide subsets of existing/current results and allow to step in/out of facets) Problems / Challenges: 1. Translatability: if staff changes or add new labels, they will not be translated 2. same files for elastic and Zebra -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 74

[Bug 18235] New: Elastic search - Configurable facets
by bugzilla-daemon＠bugs.koha-community.org 21 Jan '26

21 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18235 Bug ID: 18235 Summary: Elastic search - Configurable facets Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Searching Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 14899, 17169, 18174 >From the Elastic mappings configuration page, the librarians should be able to manage facets (display/hide and order). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14899 [Bug 14899] Mapping configuration page for Elastic search https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17169 [Bug 17169] Add facets for ccode to elasticsearch https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18174 [Bug 18174] Add the Koha::Object->update method -- You are receiving this mail because: You are watching all bug changes.

1 137

[Bug 28245] New: Language dropdown in advanced search should be sorted
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '26

20 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28245 Bug ID: 28245 Summary: Language dropdown in advanced search should be sorted Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org The Language dropdown in the advanced search should be sorted. It should be sorted according to the locale of the user. For instance, sorting by iso 629-2 codes favours English. Take for example "German". The code is "ger" and in English it's "German" but in French it's "Allemand", and in German it's "Deutsch". The alphabetical sort should be done to align with the expectations of the language of the user/interface. I'm not sure what to do about non-alphabetic languages like Chinese that don't do alphabetic sorting... Also, this is neat https://perldoc.perl.org/Unicode::Collate::Locale. A core module which adds support for locales. That said, sort for French is weird. The first is normal sort() and the second is Unicode::Collate::Locale sort. $VAR1 = [ 'a', 'e', 'ç', 'é', 'ï' ]; $VAR1 = [ 'a', 'ç', 'ï', 'é', 'e' ]; -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 29194] New: Patron messaging preferences should be ordered
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '26

20 Jan '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29194 Bug ID: 29194 Summary: Patron messaging preferences should be ordered Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 28153 comment 3 suggests the preferences should be ordered Alphabetical could differ in different languages, and I think that would be confusing I would suggest a 'logical' ordering - Holds options together, ILL options together, and item option in process order: Checkout, Predue, Due, Checkin Currently the table is ordered by 'message_attribute_id' and these is not a simple way to sort as desired -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34