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

[Bug 38310] New: DataTables - Use Select2 for column filters
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38310 Bug ID: 38310 Summary: DataTables - Use Select2 for column filters Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 36640 We should apply Select2 to all of dropdown lists present in the column filters. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36640 [Bug 36640] Upgrade DataTables from 1.13.6 to 2.x -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 34976] New: Encryption keys should not be shared between modules
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34976 Bug ID: 34976 Summary: Encryption keys should not be shared between modules Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org At this time we are using the encryption key in koha-conf to encrypt stuff for 2FA, EDI and Acquisition already. The key was introduced for 2FA. I think that it would be better to differentiate and use separate keys for various processes in Koha. For instance, the key for 2FA should be used exclusively for that purpose. We could consider if that is needed also for EDI and Acq since these are related modules. They could use one or two new keys. When adding a new call to Encryption, we should think about it. Perhaps this would be forced a bit more by passing a parameter to K::E indicating which key to use? Opening the discussion :) What do you think? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 36884] New: Make it possible to use the record_source as a criteria for a search
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36884 Bug ID: 36884 Summary: Make it possible to use the record_source as a criteria for a search Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I'm not sure what would be the more efficient, using SQL and the ORM or add some ES index, but we need to have a way to find all records which belongs to a record_source. It would as well be nice to be able to do a batch edit to change the source of a record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 42197] New: Item search results : display in the filters only values from the results
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42197 Bug ID: 42197 Summary: Item search results : display in the filters only values from the results Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: laurence.rault(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In item search results, dropdown are displayed at the top of the colums to be able to filter the results. However, all the existing values (authorised values, itemtypes, branches) are displayed here, with sometimes very long lists (of locations for example). It would be better if only values existing in the results were proposed in the dropdown. Add also a value "Empty", to be able to display only the results with empty or null values for the column. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 32609] New: Remove compiled files from src
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32609 Bug ID: 32609 Summary: Remove compiled files from src Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We need to improve our yarn build commands to generate css and js compiled files. Then remove them from our codebase, and generate them when needed: - when generating the debian packages - when ktd is starting up - when patches are applied on the sandbox -- You are receiving this mail because: You are watching all bug changes.

1 104

[Bug 38779] New: Record sources not working on packages install
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38779 Bug ID: 38779 Summary: Record sources not working on packages install Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Interestingly, we miss `record_sources.js` in Makefile.PL Seen this on a packages install: [2024/12/23 10:26:39] [WARN] File not found : js/vue/dist/admin/record_sources.js at /usr/share/koha/lib/Koha/Template/Plugin/Asset.pm line 84. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 42395] New: Missing translations on load_patron_holds_table
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42395 Bug ID: 42395 Summary: Missing translations on load_patron_holds_table Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com The load_patron_holds_table() datatable is missing some translation tags. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 41829] New: Tag editor button has wrong id on copied MARC field when value builder plugin is used
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41829 Bug ID: 41829 Summary: Tag editor button has wrong id on copied MARC field when value builder plugin is used Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Noticed this when testing bug 39522. When one copies MARC field, Tag editor button on fields containing value builder plugin have same id as original MARC field. To reproduce: 1. Find MARC framework which has value builder plugin attached to one of its fields. 2. Navigate to Cataloging -> New record. 3. Navigate to MARC field with plugin attached to it. 4. Inspect fields Tag editor button with browsers developer tools. -> Check the id of Tag editor button. 5. Copy the field and check id of copied Tag editor button. -> Notice that it has the same id as in original field. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 26815] New: QueryFuzzy should also fuzzy Elasticsearch searches when set to "try"
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26815 Bug ID: 26815 Summary: QueryFuzzy should also fuzzy Elasticsearch searches when set to "try" Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com When set to "Try" QueryFuzzy should try to Fuzzy searches on Elastic without making staff and patrons always add a ~ after each search term. Elastic has support for fuzzy search https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-f… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 35766] New: Allow staff to adjust privacy settings for patron
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35766 Bug ID: 35766 Summary: Allow staff to adjust privacy settings for patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Okay, right off the bat, let me make this clear. I am not asking for staff to control whether they can see patron history. What I am asking is for a setting to allow staff to set the privacy setting for the patron. We have need for our homebound patrons to retain history so that the check for previous checkouts works. Some, if not most, of the homebound patrons may not be tech savvy enough to go into their account and turn this on. We can default the homebound patron to retain this setting, but we have no way within the patron account to flip the switch for existing patrons. I am pretty sure this was by design. If it is of concern, a compromise might be to have a "Request to turn on history" email sent to the patron, in which they can click a link to confirm consent. Maybe also a reject, in which the link to request in the patron account would show the date the request was last rejected. Staff would have the option to request again, and if rejected again, the date would be updated. Thoughts? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24