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

[Bug 30312] New: letter.pl All libraries selection should only show All libraries
by bugzilla-daemon＠bugs.koha-community.org 28 Apr '26

28 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30312 Bug ID: 30312 Summary: letter.pl All libraries selection should only show All libraries Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org This page drives me nuts. It would be appreciated if the "All libraries" selection would only show the templates that are for (All libraries). Maybe it should be changed to "Defaults" to show (All libraries), and have the (All libraries) show everything. Either way, it would be helpful to change this so you could see it one way or the other. The way it is now is maddening. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 25390] New: Login box is removed from opac-main.tt if Shibboleth or CAS is enabled
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25390 Bug ID: 25390 Summary: Login box is removed from opac-main.tt if Shibboleth or CAS is enabled 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On the OPAC main page (opac-main.tt) if CAS or Shibboleth are enabled than we remove the login box on the right side of the page (#login). I am wondering if this is necessary: 1. It does not remove local login functionality as you can still login via the modal in the top right corner. 2. In multi library systems this can be a problem as some might use a SSO service while others would like to see the login box on the right side. 3. Maybe it would be simpler to keep the login box regardless of sign in method and hide it via CSS for libraries that don't want it? -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 39961] New: koha-create doesn't start all queues
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39961 Bug ID: 39961 Summary: koha-create doesn't start all queues Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal 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 To reproduce: 1. Run: $ ktd --shell k$ sudo koha-create --create-db test => FAIL: No mention to `long_tasks`: ``` Koha instance is empty, no staff user created. Restarting Apache httpd web server: apache2. Starting Koha worker daemon for test (default):. Starting Koha indexing daemon for test:. ``` -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 27785] New: Point of sale needs a note field
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27785 Bug ID: 27785 Summary: Point of sale needs a note field Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org In the patron account, when making a payment, you have a note field. This note field was left off the Point of sale interface. This is REALLY NEEDED. We have a payment type of Check that we offer because, we accept checks. It is this note field where we record the check number. WE REALLY NEED THIS NOTE FIELD! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 17772] New: Allow to sort lists by date the record was created
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17772 Bug ID: 17772 Summary: Allow to sort lists by date the record was created Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Lists in OPAC and staff can be sorted by different fields. It would be nice if we could offer 'date created' as an additional option for sorting. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 39557] New: Normalize MARC21 XML metadata into structured MySQL database tables via Koha Plugin
by bugzilla-daemon＠bugs.koha-community.org 27 Apr '26

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39557 Bug ID: 39557 Summary: Normalize MARC21 XML metadata into structured MySQL database tables via Koha Plugin Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)trust-box.at QA Contact: testopia(a)bugs.koha-community.org The proposed plugin (Koha::Plugin::HKS3::NormalizeMARC2DB) aims to normalize MARC21 XML metadata from the biblio_metadata.metadata table into structured MySQL database tables. Currently, MARC21 XML is stored as a single XML blob, making advanced querying, reporting, and integration difficult. This plugin introduces an automatic normalization step triggered by the after_biblio_action hook whenever metadata is added or modified. It splits MARC XML into normalized relational tables fully supporting repeatable fields, subfields, and indicators. Advantages: Significantly simplifies complex querying and reporting of MARC21 data. Enhances data integrity and consistency. Facilitates integration with external reporting tools, analytics, and applications. Improves database performance for MARC metadata queries. Provides clear and structured access to MARC data elements. This approach aligns with best practices for database normalization and can substantially enhance Koha's extensibility and interoperability. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 39732] New: Remove MarcRecordFromNewSuggestion from C4/Suggestions.pm
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39732 Bug ID: 39732 Summary: Remove MarcRecordFromNewSuggestion from C4/Suggestions.pm 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: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23990 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 37829] New: Allow additional fields for bookings
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37829 Bug ID: 37829 Summary: Allow additional fields for bookings Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.derscheid(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Directly from LMSCloud's requirements: > As a Koha library, we want to be able to use configurable additional fields for bookings in order to enable patrons to provide additional information with bookings like the persons who need to be informed when the material is available or a contact person of the institution. > The additional fields will be editable and stored with the booking and should be also available in booking notifications. I think this is interesting because these use-cases seems like a perfect fit for the bookings feature. For example when working with schools or something of the like. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 39872] New: Patron club holds - autocomplete does not work
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39872 Bug ID: 39872 Summary: Patron club holds - autocomplete does not work Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When placing a hold for a patron club, the autocomplete for the patron club does not work in the same way that searching for a patron does. The text on the clubs tab says "Enter club ID or partial name". I would expect this to work the same way or similar to the patron autocomplete. What happens instead: 1. If there is only one club that matches, the hold details page is populated with the club details and members. 2. If there is more than one matching club, or you press search without any search text, it lists the available clubs. To replicate: 1. Create a patron club: 1.1 Go to Tools > Patrons and circulation > Patron clubs 1.2 Add a club template: . + New club template . Name: BOOK . Description: Template for book clubs . Save 1.3 Add a club: . + New club > BOOK . Name: SCIFI . Description: Science fiction book club . Save 2. Add a patron to the club: 2.1 Go to a patron's record, for example Mary Burton 2.2 Go to Details > Clubs tab 2.3 Click + Enroll for the SCIFI club 2.4 Click Finish enrollment to complete the enrollment 3. Place a hold for a club: 3.1 Go to any record with items, for example 'The hydrogen sonata' (biblionumber = 333) 3.2 Place a hold: Place hold 3.3 Click the clubs tab 3.4 Note that the instructions say "Enter club ID or partial name" 3.5 Start typing science or sci 3.6 Note that no values are shown, like search for a patron name does on the patrons tab 3.7 Click search 3.8 Since there is only one club, it populates the hold details page and lists the club members 3.9 Note that if you don't type anything and click search, you get a list of all clubs to choose from -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 39942] New: Hold found (item is waiting and in transit) is ambiguous
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '26

25 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39942 Bug ID: 39942 Summary: Hold found (item is waiting and in transit) is ambiguous Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: anneli.osterman(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Created attachment 182655 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=182655&action=e… Screenshot of the transfer dialogue When you try to transfer an item that is trapped to a hold and in transfer to another branch (to the pickup location) you will get a dialogue box that says Hold found (item is waiting and in transit) https://gitlab.com/koha-community/Koha/-/blob/main/koha-tmpl/intranet-tmpl/… This is confusing because item/hold cannot be waiting AND in transit at the same time. And the hold is actually not yet waiting in this stage. Should this be changed to a more accurate form? Something like: Hold found (item is in transit to the pickup location) -- You are receiving this mail because: You are watching all bug changes.

1 4