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

[Bug 29710] New: Add cancellation reason to OPAC holds history
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '25

01 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29710 Bug ID: 29710 Summary: Add cancellation reason to OPAC holds history Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: axelle.clarisse(a)univ-amu.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 26281 adds the cancellation reason to the holds history page in the staff interface. It would be useful to have the same dev on the holds history page on the OPAC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 40421] New: Logged in info should be data-attributes instead of text
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '25

01 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40421 Bug ID: 40421 Summary: Logged in info should be data-attributes instead of text Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We have these in the HTML on the staff interface: loggedinusername loggedincategorycode logged-in-branch-code Instead of display that info as text in the HTML element we should use data-attributes. One big benefit to using data-attributes would be that these could then be selectable with CSS. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 39951] New: No filter for Name column in licenses table in ERM
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '25

01 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39951 Bug ID: 39951 Summary: No filter for Name column in licenses table in ERM Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: roman.dolny(a)jezuici.pl QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, pedro.amorim(a)openfifth.co.uk To reproduce: 1. Enable ERMModule. 2. Add Lincense (with vendor) and show table with licences. 3. Note no text input filter for column Name. There should be one. 4. Note that filters for columns Vendor, Description, Type, Status are left-shifted (dropdown list with vendors is in column Name, and so on). They should be moved one column right. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 40573] New: Remove link for "Get desktop application" if app no longer maintained
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '25

01 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40573 Bug ID: 40573 Summary: Remove link for "Get desktop application" if app no longer maintained Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com I followed the link for "Get desktop application" on the circulation home page, and noticed the app hasn't been updated in 10 years and the last release was in 2016. If the app isn't maintained/supported anymore, then we should remove the link. Hopefully Bywater can provide some insight here. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 40558] New: Issue After Upgrading Koha from 25.05.01 to 25.05.02 – Patron Search Error
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '25

01 Aug '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40558 Bug ID: 40558 Summary: Issue After Upgrading Koha from 25.05.01 to 25.05.02 – Patron Search Error Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: ddvala9(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com After upgrading Koha from version 25.05.01 to 25.05.02, we are encountering an issue while searching for patrons by name. The following error message appears: Error Message: “Something went wrong when loading the table. 500: Internal Server Error. Not in enum list: yes, no, inherit.” However, searching by library card number works without any issue. Kindly look into the matter and advise on a resolution. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 40571] New: Should LocalHoldsPriority be changed to HoldsPriority?
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '25

31 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40571 Bug ID: 40571 Summary: Should LocalHoldsPriority be changed to HoldsPriority? Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Since LocalHoldsPriority has expanded to groups, it isn't necessarily a "local" thing anymore. Should it be renamed to just HoldsPriority or HoldPriorities? Very trivial, I know. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 11591] runtime parameter for library groups
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '25

31 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11591 George Williams (NEKLS) <george(a)nekls.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |george(a)nekls.org --- Comment #4 from George Williams (NEKLS) <george(a)nekls.org> --- Yes. This would be a great feature for Koha installation with multiple branches but when Nicole wrote the original bug I think there were only two types of groups - Search Domain groups and Library Property groups. Groups have expanded now to include - Limit patron data access by group (ft_hide_patron_info) - Limit item editing by group (ft_limit_item_editing) - Use for OPAC search groups (ft_search_groups_opac) - Use for staff search groups (ft_search_groups_staff) - Is local hold group (ft_local_hold_group) - Is local float group (ft_local_float_group) So any work on adding runtime parameters for library groups to the Reports module is going to need to include a way to specify which type of group the parameter works with. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11591] runtime parameter for library groups
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '25

31 Jul '25

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

1 0

[Bug 29918] New: Batch Patron Modification - Creation of "Add Number of Days" to Expiry date field
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '25

31 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29918 Bug ID: 29918 Summary: Batch Patron Modification - Creation of "Add Number of Days" to Expiry date field Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: rcoert(a)arlingtonva.us QA Contact: testopia(a)bugs.koha-community.org It would be useful to have the Batch Patron Modification "Expiry Date" field have the option to either set a hard date or "Or add number of days:", as you do with the Batch Extend Due Dates function. Use Case: This came about from adjusting 28,500 accounts this week due to COVID closures. I had to manually adjust the dates in batches of 1000 to ensure that I didn't "over-crowd" one day with too many expiring cards. Had I been able to say extend "200 days" for each account, the dispersal of accounts could have been more randomized. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 40495] New: Add option to subject purchase suggestion API call to OPAC requirements
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '25

31 Jul '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40495 Bug ID: 40495 Summary: Add option to subject purchase suggestion API call to OPAC requirements Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com There are several ways to restrict purchase suggestions made via the Koha OPAC relative to suggestions made via the staff interface. Suggestions made via the API don't respect any of those options. We should add a header parameter to the Add Suggestion API call to make a request subject to those options. AnonSuggestions - if disabled, OPAC purchase suggestions require a borrowernumber OPACSuggestionMandatoryFields - defines which fields are required suggestion - enables/disables OPAC suggestions at all suggestionPatronCategoryExceptions - blocks specific categories from making OPAC suggestions See also bug 38198, which seeks to add suggestions to BlockExpiredPatronOpacActions. When/if that happens we'd also want the option to block API suggestions for expired patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1