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

[Bug 28736] New: Better error message when ES fails to understand the syntax of the search query
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28736 Bug ID: 28736 Summary: Better error message when ES fails to understand the syntax of the search query Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: stalkernoid(a)gmail.com "Unable to perform your search. Please try again." error message doesn't provide any information to the user about the problem and can be really confusing, it implies that by simply performing the search again the result may be different somehow, while in reality the search query probably has incorrect ES syntax which will never work no matter how many times you try, asking user to "Please try again" is redundant. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 11175] Show the parent record's component parts in the detailed views
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11175 --- Comment #525 from David Cook <dcook(a)prosentient.com.au> --- Just got bitten by this: +} else { # check if we should show analytics anyway + $show_analytics = 1 if @{$biblio->get_marc_components(1)}; # count matters here, results does not } Records that shouldn't have "Show analytics" links are showing up because other records that use 773 and link by biblionumber/controlnumber still index to Host-item index using 773$t, and the 245$t from my first record gets hits for unrelated records that have indexed their 773$t into Host-item. Fun times. I'll have to look to see if there's any related reports here that just aren't linked to this one... and failing that I'll think of a solution... -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38623] New: Suggestion management page does not show preferred name
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38623 Bug ID: 38623 Summary: Suggestion management page does not show preferred name Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Depends on: 28633 Bug 28633 added a "preferred name" field to patrons, which was meant to be displayed instead of the first name (if enabled) whenever a patron name is displayed in the staff interface, with the first name being visible only on the patron's account details page. The purchase suggestions table is still displaying the first name in the "Suggested by", "Managed by", and "Last modification by" columns. The form for editing a purchase suggestion is also displaying the first name for the suggestor and suggestion manager. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 [Bug 28633] Add a preferred name field to patrons -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 8179] Receiving multiple order lines at once
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8179 Felicity Brown <felicity.brown(a)montgomerycountymd.gov> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |felicity.brown@montgomeryco | |untymd.gov -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 24073] New: Allow suggestion management page to default to all libraries
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24073 Bug ID: 24073 Summary: Allow suggestion management page to default to all libraries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When looking at purchase suggestions on suggestion.pl, the default behavior is to show only suggestions for the branch one is logged in at. This can result in overlooked suggestions, especially for libraries that have more than once branch but process all suggestions at a single location. It would be good to have the option of making this page default to showing suggestions for all libraries. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 42461] New: Purchase Suggestions table actions reset library and tab after page refresh
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42461 Bug ID: 42461 Summary: Purchase Suggestions table actions reset library and tab after page refresh Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: dmeininger591(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The issue occurs within the Purchase Suggestions tables (Suggestions Management) when staff are working in a filtered view, such as: Library = Any Library Tab = Accepted, Ordered, Rejected After taking an action on a record (for example, deleting a title), the page reloads and resets to: Library = [logged in library] Tab = first/default tab Instead of preserving the staff member’s previous context. This creates extra navigation steps and slows workflows when processing multiple suggestions. Steps to Reproduce 1. Go to the Suggestions module in the staff interface (Home > Acquisitions > Suggestions). Notice the default library selection is logged in library. 2. Select a different library or 'Any Library' 3. (Optional) Click into a non-default tab (for example, Ordered) 4. Edit an item and then cancel out of the edit. Observe where the page reloads After the action completes, the system redirects to: Library = Logged In Library Tab = default/first tab The user must manually return to: Any Library the previously selected tab After completing an action within a tab, the system should remain in the same tab and library context the user was working in. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 12155] shelving location changes when floating
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12155 carthur(a)slolibrary.org <carthur(a)slolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carthur(a)slolibrary.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 28116] New: Allow for Floating Items to float even if cancelled from Holds
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28116 Bug ID: 28116 Summary: Allow for Floating Items to float even if cancelled from Holds Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, if a library would like to float all their items and this is set up in the circulation rules when a hold is canceled that had been previously transferred, Koha will want to send that back to the Home Library. 1. Set up Item Floats in Circ Matrix 2. Place a hold on an item that needs to be transferred. 3. Trigger that item and transfer to the patron's preferred pickup branch. 4. Hold has arrived at Branch- but now patron cancels the hold. 5. Staff see "Cancel Hold and Transfer back to Home Location" They would like to see Cancel Hold and Koha to understand that they would like to keep the item now at this current location instead of sending it back to the Home. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 42190] New: Add datatables to reports
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42190 Bug ID: 42190 Summary: Add datatables to reports 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: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com Markus made a really neat datatables plugin: https://github.com/mpathy/KohaDatatables4Reports/tree/main I think it would be a great feature for core Koha. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 69

[Bug 42769] New: Add a SIP testing tool to the staff web interface
by bugzilla-daemon＠bugs.koha-community.org 03 Jun '26

03 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42769 Bug ID: 42769 Summary: Add a SIP testing tool to the staff web interface Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Now that the SIP configuration is mostly in the staff interface, it would be very useful to have a tool not for testing SIP connectivity, but for checking the response value for the various custom template fields we have. I'm imagining a tab within the account editor ( for saved accounts ) where we can enter things like patron and item barcodes to test the generated response. It would be even better if we could wrap that in a transaction so it doesn't actually do anything, but I have the feeling that may prove infeasible. Such a testing tool would eliminate the need for someone to know the password for the SIP account in order to develop and test the various templates and options for that account. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2