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

[Bug 38061] New: Serials collection table improvements
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38061 Bug ID: 38061 Summary: Serials collection table improvements 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: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 67

[Bug 37538] New: Improve documentation of connexion_import_daemon.pl
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37538 Bug ID: 37538 Summary: Improve documentation of connexion_import_daemon.pl Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: rudolfbyker(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Patch incoming :) See related discussions at: - https://chat.koha-community.org/koha-community/pl/o18q57a1pt879dgp63ujtcajpe - https://chat.koha-community.org/koha-community/pl/gz3mjusns3bdme3j4f8sp83sfw - https://chat.koha-community.org/koha-community/pl/yzxmrfegcbnrjgqgjt7t6wjwhy I plan to follow this up with a patch for the koha-manual, which I will also link here. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 37099] New: Add uniform title fields to the title and subject Elasticsearch index mappings
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37099 Bug ID: 37099 Summary: Add uniform title fields to the title and subject Elasticsearch index mappings 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: aleisha(a)catalyst.net.nz We would like: A 'title' or 'title as phrase' search to also search on the following Uniform Title fields: * 130$a * 240$a * 730$a A 'subject' or 'subject as phrase' search to also search on the following Uniform Title fields: * 630$a -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 36849] New: Add more tags to Elasticsearch mapping for title, title as phrase
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36849 Bug ID: 36849 Summary: Add more tags to Elasticsearch mapping for title, title as phrase 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: aleisha(a)catalyst.net.nz Libraries may expect a 'title' search to look at a few other tags that aren't currently mapped. To the title index for MARC21, we would like to additionally map: * 440a * 600t * 800t * 810t * 830np -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 35192] New: Highlight search terms in OPAC Title notes tab
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35192 Bug ID: 35192 Summary: Highlight search terms in OPAC Title notes tab 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: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org It would be nice if Koha could highlight the search term in the title notes tab of a OPAC biblio detail page. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 32736] New: koha-worker should be able to restart all queues with a single call
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32736 Bug ID: 32736 Summary: koha-worker should be able to restart all queues with a single call Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Maybe a --queue all or something? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 32483] New: Show requested changes to personal details in OPAC
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32483 Bug ID: 32483 Summary: Show requested changes to personal details in OPAC 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment when a user makes a request for changing the address or similar, there is a note on submitting the form, that the request will be forwarded to the library for processing. After that, when the page is reloaded, the old information still shows and there is no hint on a pending change request. It would be nice if we could show that there was still a change request pendingon the page, so that people don't resend them unnecessarily. And it would be great if we could show which changes were requested. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 26993] New: Allow StoreLastBorrower to retain up to 2 previous patrons
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26993 Bug ID: 26993 Summary: Allow StoreLastBorrower to retain up to 2 previous patrons 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 14945 Various workflows and circumstances can result in the "last returned by" value stored by StoreLastBorrower getting overwritten sooner than a library might like. For example, a patron may find the item they've checked out was damaged by the previous patron. They put the item in the bookdrop on their way into the library and then alert staff to the damage when they check out their next batch of items. By that time, the damaged item has been checked in, our imaginary patron shows as "last returned by," and we have no record there of who had it previously. We could alleviate this by adding a third option to the StoreLastBorrower system preference, so that one can choose "Do not store," "store 1," or "store 2." This entire feature would still be optional for libraries that don't want to keep this data. Additionally, bug 23260 is adding the ability to clear this data after a period of time using cleanup_database. These factors help mitigate the privacy concerns inherent to the matter. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14945 [Bug 14945] Add the ability to store the last patron to return an item -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 84

[Bug 42105] New: Don't count items with waiting holds as available
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42105 Bug ID: 42105 Summary: Don't count items with waiting holds as available Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com To reproduce in KTD: - Set OPACHoldsIfAvailableAtPickup = Don't allow - Find a record with one item in the staff interface (e.g. "Programming Perl") and place a hold on it, e.g. for Edna Acosta - Log in to the OPAC as a diferent user and find the same record - Try to place a hold on the record - The "Pick up location" will have one element and it will be grayed out. - If you hover over the library in the dropdown there will be a "tooltip" that says "At least one item is available at this library". But the waiting item should not be counted as available. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 --- Comment #411 from Martin Renvoize (ashimema) <martin.renvoize(a)openfifth.co.uk> --- Created attachment 195432 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=195432&action=e… Bug 10190: Fix false conflict error when editing specific trigger rules When editing a specific rule (e.g. */Kids/Books) alongside an all/all/all rule, the conflict check incorrectly reported a conflict. The effective=true API response always returns context as */*/* (fallback), so ruleSetInDb.context differed from currentRuleSet.context (which was overridden to the real context). Fix by overriding ruleSetInDb.context before the hasConflict comparison, consistent with the existing pattern in setCurrentRuleSet. -- You are receiving this mail because: You are watching all bug changes.

1 0