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

[Bug 42205] New: Field 001 in Authorities cannot be set freely
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42205 Bug ID: 42205 Summary: Field 001 in Authorities cannot be set freely Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: mark(a)hofstetter.at QA Contact: testopia(a)bugs.koha-community.org In Authorities you cannot set the value of Marc Field 001, it is filled with the database id (authid) from the table. This is wrong from a technical point of view (db ids shouldn't have a meaning in the real world) But more important it make it hard to import linked bibliographic and authority, because you know the authid only after the import. So I propose to add the abilty to chose the 001/controlnumber freely and have it accessable in the auth table -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 42158] New: Overdue notice trigger setup offers too many letter options
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42158 Bug ID: 42158 Summary: Overdue notice trigger setup offers too many letter options Initiative type: --- Sponsorship --- status: 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: chloe.zermatten(a)openfifth.co.uk, lisette(a)bywatersolutions.com, martin.renvoize(a)openfifth.co.uk, nick(a)bywatersolutions.com When setting up overdue notices, the letter dropdown includes all notices with module Circulation. That gives a very long list of options that includes several templates that are hardcoded for other processes (like DUE and PREDUE). It would be helpful to shorten that list. Maybe we could define a new letters module value of Overdues? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 9150] Add id and relevance as sort options for authorities search
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9150 --- Comment #4 from Fridolin Somers <fridolin.somers(a)biblibre.com> --- (In reply to cgresser from comment #3) > I would second this, as searching authorities can be hard for more complex > authorities (i.e. with more than 2 or 3 elements). Please consider as a > much-wanted enhancement. > Clemens You mean sorting by authority type ? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 36393] New: Renewal with a specific date does not take the new date due that we pick
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36393 Bug ID: 36393 Summary: Renewal with a specific date does not take the new date due that we pick Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce 1- Log in to the staff interface 1-1. Make sure you have a ciculation rule that allows you to renew 1-2. set the AllowRenewalLimitOverride system preference to Allow and SpecifyDueDate to Allow 2. Check out the item to a Borrower 5. Access the borrower's account and renew it until the limit is reached and note the due date. 6. Go to Circulation, click Renew 7. Enter the item barcode and choose a due date further than the due date from step 5 and submit 8. Click on Override limit and renew button ---> Note that the new date due is not the date that we picked in step 7 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 37189] New: Renewals: Koha prioritizes hard due date from circulation rules over manual due date, although the manual due date is earlier
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37189 Bug ID: 37189 Summary: Renewals: Koha prioritizes hard due date from circulation rules over manual due date, although the manual due date is earlier Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: isabel.pineda(a)ds.edu.sv QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I wrote this comment last week in Bug 36393, but I am not sure if this bug is still being attended, so I decided to file a new bug. Please delete it if it is duplicated: After updating from version 23.11 to 24.05, the renewal for a specific date is not working anymore. Although I give a specific date for a specific renewal, the system takes automatically the hard due date from the circulation rules. e.g. In "Administration > Circulation rules" I save "15.08.2024" as hard due date for a specific item type and patron category. Then I go to one patron of the above category to renew his borrowed items, and manually select "30.07.2024" as due date. -> The system renews the items until 15.08.24. It ought to prioritize the manual due date for this specific patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 40596] New: Migrate CAS and Shibboleth into the identity providers
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40596 Bug ID: 40596 Summary: Migrate CAS and Shibboleth into the identity providers Change sponsored?: --- Product: Koha Version: Main 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When we envisioned the bug 31378 implementation, it was designed to cover other protocols as well. I'm filing this report to work on this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 78

[Bug 40560] New: Incorrect breadcrumb on recall history
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40560 Bug ID: 40560 Summary: Incorrect breadcrumb on recall history Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It is still using the "old way" and is not looking good: https://snipboard.io/uo10iU.jpg -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 41908] New: Migrate LDAP configuration into Identity Providers
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41908 Bug ID: 41908 Summary: Migrate LDAP configuration into Identity Providers Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: dcook(a)prosentient.com.au, hagud(a)orex.es, kyle(a)bywatersolutions.com, magnus(a)libriotech.no, martin.renvoize(a)openfifth.co.uk, matthias.meusburger(a)biblibre.com, nick(a)bywatersolutions.com, oliver.behnke(a)aei.mpg.de, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 40596 When we envisioned the bug 31378 implementation, it was designed to cover other protocols as well. I'm filing this report to work on this. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40596 [Bug 40596] Migrate CAS configuration into Identity Providers -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 38116] New: Patrons search description should be built from DT's search settings
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38116 Bug ID: 38116 Summary: Patrons search description should be built from DT's search settings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 38112 We are building a description of the search on top of the patrons search table. But this is not accurate and does not reflect the exact search result that is displayed in the table. This is because column filters can used after we submitted the form (on the left). We could try to build it using DT's search settings, and it would then even be possible to have it for all tables. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38112 [Bug 38112] Description of patrons search no longer displayed -- You are receiving this mail because: You are watching all bug changes.

1 40

[Bug 41669] New: Elasticsearch mappings should have user_edited flag
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41669 Bug ID: 41669 Summary: Elasticsearch mappings should have user_edited flag Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Out of the box, Elasticsearch's mappings in the database are populated by the mappings.yaml. It's alwasy possible to re-populate the database by "resetting" the configuration. You often need to do this after an upgrade to get all the new defaults. But if you do that, you lose all your customizations. It would be nice to have a "user_edited" to denote mappings that have been added/edited by users via the web UI. Having a visual cue that these are custom fields would be great. (If we had an option to retain those fields during a reset, that would be even more amazing. Although that's more complicated.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6