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

[Bug 39819] New: Additional performance improvements for when loading borrower relationships.
by bugzilla-daemon＠bugs.koha-community.org 05 May '25

05 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39819 Bug ID: 39819 Summary: Additional performance improvements for when loading borrower relationships. Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com >From Nick via Bug 39644: I think there is more cleanup to be done here. relationships_debt is only called twice in the code base: once in moremember.pl once in Koha::Patron->is_patron_inside_charge_limits (which is also called in moremember) The two calls are: - moremember: $patron->relationships_debt( { include_guarantors => 0, only_this_guarantor => 1, include_this_patron => 1 } ); - is_patron_inside_charge_limits: $patron->relationships_debt( { include_guarantors => 1, only_this_guarantor => 0, include_this_patron => 1 } ); The difference being that the first returns only the single patrons fine + their guarantees, the latter returns the patron and thier gusarantees and the guarantees other guarantors The first being a subset of the second, we should be able to return this additional info from "is_patron_inside_charge_limits" and avoid a double call. Additionally, moremember does checks against "NoIssuesChargeGuarantorsWithGuarantees" and "NoIssuesChargeGuarantees" - both of which are checked inside "is_patron_inside_charge_limits" so we can simply use values we are already calculating and not calculate them again -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 35832] New: Add option to include an email signature on all notices
by bugzilla-daemon＠bugs.koha-community.org 04 May '25

04 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35832 Bug ID: 35832 Summary: Add option to include an email signature on all notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org It would be useful to have the option to always include a particular signature on all notices from the system. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 38747] New: Have consistent signature in sample notices
by bugzilla-daemon＠bugs.koha-community.org 04 May '25

04 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38747 Bug ID: 38747 Summary: Have consistent signature in sample notices Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org We currently have a plethora of signature styles across sample notices. It would be nice to make them consistent. Here are the ones I found in the sample_notices.yaml file (I skipped the slips and sms messages) Notices meant for patrons - branchname Staff (ODUE) - Kind regards branchname (BOOKING_CANCELLATION, BOOKING_MODIFICATION, BOOKING_CONFIRMATION) - Kind regards full branch address (ILL_PICKUP_READY, ILL_REQUEST_UNAVAIL, ILL_REQUEST_UPDATE, ILL_PICKUP_READY, ILL_REQUEST_UNAVAIL) - Thank you (TICKET_ACKNOWLEDGE, TICKET_RESOLVE, TRANSFER_OWNERSHIP) - Thank you, branchname (ACCEPTED, AVAILABLE, ORDERED, REJECTED) - Thank you, Librarian branchname (MEMBERSHIP_EXPIRY) - Thank you, Your library, branchname (MEMBERSHIP_RENEWED) - Thank you. (CHECKIN, DUEDGST, PREDUEDGST, PASSWORD_RESET,STAFF_PASSWORD_RESET) - Thank you. Your library. (SHARE_ACCEPT, SHARE_INVITE) - Thank you! (AR_COMPLETED, AR_PENDING, AR_REQUESTED, AR_PROCESSING, HOLDDGST, RETURN_RECALLED_ITEM, PICKUP_RECALLED_ITEM, HOLDPLACED_PATRON) - Thank you for visiting branchname. (CHECKOUT, RENEWAL) - Your library. (ACQ_NOTIF_ON_RECEIV, PASSWORD_CHANGE) - Your library (AR_CANCELED, 2FA_DISABLE) - No signature (ACCOUNT_PAYMENT, ACCOUNT_WRITEOFF, DUE, PREDUE, DISCHARGE,OPAC_REG_VERIFY, WELCOME, 2FA_OTP_TOKEN, CANCEL_HOLD_ON_LOST, HOLD, HOLD_REMINDER, NEW_CURBSIDE_PICKUP, SERIAL_ALERT, AUTO_RENEWALS, AUTO_RENEWALS_DGST, LIST, CART) Notices meant for staff, other libraries, vendors, etc. - Thank you (TICKET_ACKNOWLEDGE, TICKET_RESOLVE) - Thank you, branchname (ACQORDER, TO_PROCESS, NOTIFY_MANAGER) - Kind regards full branch adress (ILL_PARTNER_REQ) - Your library (2FA_DISABLE) - No signature (TICKET_ASSIGNED, TICKET_NOTIFY, CHECKOUT_NOTE, ACQCLAIM, ILL_REQUEST_CANCEL, ILL_REQUEST_MODIFIED, ILL_REQUEST_CANCEL, ILL_REQUEST_MODIFIED, HOLDPLACED, HOLD_CHANGED, NEW_SUGGESTION, PROBLEM_REPORT, OPAC_REG, OAI_HARVEST_REPORT) Is there any that would fit all of them? I like "Thank you, branchname" provided the branch is available for the notice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 38090] New: The UX for customer notice styling per notice template is confusing
by bugzilla-daemon＠bugs.koha-community.org 03 May '25

03 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38090 Bug ID: 38090 Summary: The UX for customer notice styling per notice template is confusing Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org A couple of people have highlighted now that the adding of a 'Format' section amongst the message transport types in the notice template editor is confusing. The feature itself is also a little misleading as people presumed from the title that it affected print-type notices only, when in fact it affects all notice types when printed. The distinction is subtle, but makes a large difference in expectations. I'm not sure how to proceed here, but I want it recorded as a bug to see if anyone can come up with a cleaner approach for end users. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 17406] New: Simplify pay.pl interface - pt.1
by bugzilla-daemon＠bugs.koha-community.org 03 May '25

03 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17406 Bug ID: 17406 Summary: Simplify pay.pl interface - pt.1 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I think we can simplify the payment screen. 1) Remove the Pay Amount button. By default, all items are selected, so the Pay selected will do the job. 2) Remove the cancel link. A) It's a link, not a button. B) All it does is change tabs. There isn't anything to really cancel. Changing tabs or navigating elsewhere does the same thing. 3) Remove Write off all button and replace with Write off selected button. 4) Remove the individual Pay and Write off buttons. They are redundant. #4 is my opinion, but they really convolute the flow. The checkboxes and two buttons are sufficient and straight forward. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 39821] New: Add visual clue for IncludeSeeAlsoFromInSearches like IncludeSeeFromInSearches
by bugzilla-daemon＠bugs.koha-community.org 03 May '25

03 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39821 Bug ID: 39821 Summary: Add visual clue for IncludeSeeAlsoFromInSearches like IncludeSeeFromInSearches Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org The advanced search gives a visual indication in the staff interface when IncludeSeeFromInSearches is enabled (see screenshot in the Manual https://koha-community.org/manual/latest/en/html/searchingpreferences.html#…) It would make sense for IncludeSeeAlsoFromInSearches to have the same effect when enabled. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 35597] New: Purchase Suggestion changes aren't logged
by bugzilla-daemon＠bugs.koha-community.org 03 May '25

03 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35597 Bug ID: 35597 Summary: Purchase Suggestion changes aren't logged 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: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org IT would be helpful if changes to purchase suggestions were logged. Sometimes troubleshooting the cycle of a suggestion. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 39818] New: Add TT notices to serial issues claim
by bugzilla-daemon＠bugs.koha-community.org 02 May '25

02 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39818 Bug ID: 39818 Summary: Add TT notices to serial issues claim Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org It would be great to be able to use TT syntax in notices to claim serial issues. It seems that there is no community default for this module, but librarians can create their one by going to Tools > Notices and slips > New notice and selecting the module "Claim serial issue". It looks like the serial list is not available in TT in this notices. Currently, it is inserted with the help of <item></items> For example : <item><<biblio.title>><<serial.serialseq>></item> -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 15278] [Omnibus] Port default slips and notices from bespoke syntax to Template Toolkit
by bugzilla-daemon＠bugs.koha-community.org 02 May '25

02 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15278 Marion Durand <marion.durand(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=39818 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39817] New: All list endpoints should have the x-koha-request-id parameter definition
by bugzilla-daemon＠bugs.koha-community.org 02 May '25

02 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39817 Bug ID: 39817 Summary: All list endpoints should have the x-koha-request-id parameter definition Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com This is mandatory for using them with our `kohaTable` datatables wrapper. I spotted the `/acquisitions/baskets` endpoint doesn't have it. We should have a test for it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1