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

[Bug 41410] New: Allow definition of a period after hold creation during which the hold is only filled locally
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41410 Bug ID: 41410 Summary: Allow definition of a period after hold creation during which the hold is only filled locally Initiative type: --- Sponsorship --- status: 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Currently, with local holds priority enabled the holds queue will always target an available local item if one exists; this preference is enforced before Koha consults the transport cost matrix or thinks about the Hungarian algorithm. This dev will: - add a new field to tmp_holdsqueue: local priority match - add a new system preference to enable this option and set days value for local priority period - local priority period is defined relative to when the hold was created - when the queue targets an item, add the local priority match flag if the target item is within the local holds group of the hold pickup location - at checkin, if the item could fill a hold Koha will check: -- is this item within the hold pickup group? If yes, fill hold; if no, proceed to next check -- is the hold within the local priority period? If no, fill hold; if yes, proceed to next check -- does the queue's current target have the local priority match flag? If no, fill hold; if yes, do not fill hold (look for other holds this item could fill or check item in) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61

[Bug 42827] New: Items expected column in parcels.pl always displays 0
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42827 Bug ID: 42827 Summary: Items expected column in parcels.pl always displays 0 Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: matt.blenkinsop(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The controller expects the sql to return an itemsexpected value but it never does so it always defaults to the hardcoded fallback of 0 To recreate: 1. Create an order with multiple items and receive the order in full 2. From the vendor record, click Receive shipments 3. You should be in parcels.pl and the table should show your shipments 4. The Items expected column will show 0 even though you ordered multiple items -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[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

[Bug 8137] Checkout limit for all libraries
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8137 --- Comment #165 from Mathieu Saby <mathsabypro(a)gmail.com> --- I am a bit lost. Did we really re-signoff this patch after the last changes made by Thibaud? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42230] New: DataTables search ( dt-search ) on opac-user.tt contains empty label elements
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42230 Bug ID: 42230 Summary: DataTables search ( dt-search ) on opac-user.tt contains empty label elements Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Accessibility Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, oleonard(a)myacpl.org To recreate: 1. Have a user with checkouts. holds, article requests. 2. Log into the OPAC and go to "Summary" 3. Notice the dataTables search ( dt-search ) contains an empty label: <label for="dt-search-0"></label> -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 40795] New: Fix +add note function on payment table
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40795 Bug ID: 40795 Summary: Fix +add note function on payment table Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: jheltibridle(a)rcplib.org QA Contact: testopia(a)bugs.koha-community.org Now that bug 23674 allows notes on all transactions in the transactions table, the +Add note function in the payments table can cause some additional confusion. In the payments table (pay.pl) you can click on +Add Note, but the note can't be saved unless you pay the fine in the payment screen. The same note can now be edited or saved in the transactions table in 25.05. Steps to duplicate issue: 1. Go to a patron with outstanding fines/fees 2. Go to the Make a payment tab 3. In the payments table, click +Add Note for a transaction 4. Type a note. 5. Note that there is no way to save the edit. 6. Press enter on the note, Koha takes you to the payment screen, where the changes are shown, but you must pay the fine to save the change. 7. Go to the transactions tab in 25.05. 8. Click edit and type a note and confirm 8. Go to Make a payment tab and see the note you added. The note will look like it is selected for additional editing. I would like to either see this column become uneditable (so you have to edit it in the transactions table) or have it function the same as the transactions table (have an edit button that opens a popup to edit the note). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 40201] New: Subscription search form on the start page is missing additional fields
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40201 Bug ID: 40201 Summary: Subscription search form on the start page is missing additional fields 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: clemens.tubach(a)kit.edu, michaela.sieber(a)kit.edu The searchable additional fields for subscriptions are not shown in the search form on the start page and it's easy to miss, that they can be searched from the "advanced search" that is reachable through the "more options" in the top search bar. It would be better if both forms would be consistent. To test: - Add at least one additional field for subscriptions that is searchable - Go to the serials module start page - Confirm the search form doesn't show the additional field - Click on the "More options" icon at the end of the top search bar - Click on the "Advanced search" link - Confirm that the additional fields display on this form. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 42839] New: SIP: Record SIP account/device identifier for circulation reporting
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42839 Bug ID: 42839 Summary: SIP: Record SIP account/device identifier for circulation reporting Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com Target Milestone: --- Currently SIP checkouts set the interface to 'sip', allowing reports to distinguish SIP circulation from staff client circulation. However, there is no way to distinguish between individual SIP accounts/devices used to perform those transactions. The issues.issuer_id field is not populated for SIP transactions because AddIssue only records issuer_id from the logged-in user session (C4::Context->userenv), and SIP transactions do not create a staff user session. Libraries with multiple self-check machines may wish to report on circulation activity by individual SIP account/device rather than only by branch or interface. This enhancement would provide a mechanism to record the SIP account/device identifier associated with a SIP transaction for reporting purposes. Possible implementation approaches include: - Recording the SIP account identifier in statistics. - Adding a dedicated SIP account/device field for circulation reporting. - Another implementation determined by the development community. The goal is to allow reporting by individual SIP account/device without repurposing issues.issuer_id, which is intended to reference a borrower record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 12757] Integers in saved SQL report ODT export prepended with single quote
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12757 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david(a)davidnind.com --- Comment #8 from David Nind <david(a)davidnind.com> --- Testing notes (using KTD): 1. Only opening the resulting download (.ods file) with LibreOffice Calc had the leading ' before the numbers when editing the cells (before the patch) 2. After the patch, there were no leading '. 3. Google Sheets and Office Excel (online version) opened fine before and after the patch (no formatting or alignment), without the leading '. 4. When using the "Open in DataTables" option, the download options were fine and had no leading ' when opened in LibreOffice Calc (had formatting with header row bolded and numbers right aligned), -- You are receiving this mail because: You are watching all bug changes.

1 0