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

[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 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 41605] New: Fix incorrect default value keys in Vue
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41605 Bug ID: 41605 Summary: Fix incorrect default value keys in Vue 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: matt.blenkinsop(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org We should be using defaultValue instead of value to set defaults -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 29587] New: Test mail option in SMTP servers
by bugzilla-daemon＠bugs.koha-community.org 16 Jun '26

16 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29587 Bug ID: 29587 Summary: Test mail option in SMTP servers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: vimalibre(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Dear Developers, Here is a feature suggestion to Administration > SMTP servers. Test mail option helpful for users to try newly added SMTP server works or not. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 56

[Bug 39959] New: Ability to customize the invoice table
by bugzilla-daemon＠bugs.koha-community.org 15 Jun '26

15 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39959 Bug ID: 39959 Summary: Ability to customize the invoice table Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: hdunne-howrie(a)westminster.gov.uk QA Contact: testopia(a)bugs.koha-community.org We want to be able to customize the invoice tables we see here https://wcc-rbkc-staff.koha-ptfs.co.uk/cgi-bin/koha/acqui/invoices.pl like we can for the order tables so we can add in the columns we want or hide columns as needed. In particular, we want to be able to add in total columns to this view so when we search for invoices we see the total amounts in the search results to quickly help us work out which invoice is which when we have limited information but know the total amount. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[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 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 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