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

[Bug 14806] Action Log for Modifying borrower messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '26

13 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14806 Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA --- Comment #36 from Andrew Fuerste-Henry <andrew(a)bywatersolutions.com> --- Passing QA. Thanks! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14806] Action Log for Modifying borrower messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '26

13 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14806 --- Comment #35 from Ray Delahunty <raymund.delahunty(a)outlook.com> --- Test plan point 7 puzzled me until I noticed that the diff column in logviewer is hidden be default. Once I exposed it, the before and after data appeared. I am obviously rusty signing off bugs! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14806] Action Log for Modifying borrower messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '26

13 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14806 --- Comment #34 from Community Sandboxes <sandboxes(a)biblibre.com> --- Signed off using a sandbox -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14806] Action Log for Modifying borrower messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '26

13 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14806 --- Comment #33 from Community Sandboxes <sandboxes(a)biblibre.com> --- Created attachment 207828 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=207828&action=e… Bug 14806: Log message preference changes to action logs Test plan: 1. Enable system preference BorrowersLog 2. Go to Patrons -> Edit any patron 3. Go to Messaging preferences tab 4. Update messaging preferences (e.g., change transport method, enable/disable notifications) 5. Save changes 6. Go to Tools -> Logs and verify that action logs show the messaging preference changes 7. Verify log entries show before/after values for changed preferences in diff column 8. Run the test suite: prove t/Members_Messaging.t => PASS 9. Verify that preference changes are correctly logged with the patron borrowernumber 10. Test with new patrons with patron category defaults set/unset too and verify defaults are being logged when a new parton gets saved Sponsored-by: Koha-Suomi Oy Signed-off-by: Andrew Fuerste Henry <andrew(a)bywatersolutions.com> Signed-off-by: Ray Delahunty <raymund.delahunty(a)outlook.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14806] Action Log for Modifying borrower messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '26

13 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14806 Community Sandboxes <sandboxes(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #207814|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42558] New: reserves.reservedate should be datetime instead of date
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '26

13 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42558 Bug ID: 42558 Summary: reserves.reservedate should be datetime instead of date Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In front of work I intend to do on Bug 42524. In order to calculate priorities based on reservedate, the reservedate must include time. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 96

[Bug 43378] New: Wrong hold can be selected when LocalHoldsPriority set to GiveLibraryAndGroup
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '26

13 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43378 Bug ID: 43378 Summary: Wrong hold can be selected when LocalHoldsPriority set to GiveLibraryAndGroup 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Target Milestone: --- In C4::Reserves::CheckReserves: if ( !$local_hold_match && $LocalHoldsPriority eq ('GiveLibraryAndGroup') ) { # If there's no match at the library level, check hold groups $local_hold_group_match = Koha::Libraries->find( { branchcode => $local_holds_priority_item_branchcode } )->validate_hold_sibling( { branchcode => $local_holds_priority_patron_branchcode } ); } Then: # See if this item is more important than what we've got so far if ( ( $res->{'priority'} && $res->{'priority'} < $priority ) || $local_hold_match || $local_hold_group_match ) { next Then: last if $local_hold_match || ( ( $LocalHoldsPriority eq 'GiveLibraryGroup' ) && $local_hold_group_match ); That last condition needs to OR "eq 'GiveLibraryAndGroup'" - otherwise we are setting local_hold_group_match, but not exiting the loop, and we pick the local hold group match with the highest priority -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 43623] New: Pagination of JSON Report Exports
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '26

13 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43623 Bug ID: 43623 Summary: Pagination of JSON Report Exports Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com Target Milestone: --- To avoid the risk of downloading too many rows when exporting a report as JSON, I wanted to try paginating the results by adding a limit and a variable offset (a parameter passed in the URL) to the report. But OFFSET doesn’t seem to be supported in SQL, which surprises me because it isn’t listed among the filtered keywords specified in the community wiki (create, update, etc.). Example: select itemnumber from items LIMIT 50 OFFSET 100 gives me : You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'LIMIT 0, 50' at line 2 Is it a bug ? a missing feature? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 42418] New: Add Koha::Checkin(s) â checkin as a first-class resource
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '26

13 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42418 Bug ID: 42418 Summary: Add Koha::Checkin(s) â checkin as a first-class resource Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Depends on: 41728 Blocks: 24401 Checkins in Koha are currently a side effect â they happen to checkouts, transfers, and holds, but there is no single record that captures 'a staff member scanned this item and here is what happened.' This bug introduces checkins as a proper resource: - New `checkins` table tracking the full context (who, what, where, when) and outcomes (checkout returned, transfer triggered, hold filled) - Koha::Checkin and Koha::Checkins object classes - Wire into AddReturn so every checkin path (returns.pl, SIP, API) produces a Koha::Checkin record This addresses several long-standing gaps: - 'Who checked this in?' is currently unreliable (no checkin_user_id on old_issues) - Transfers and holds triggered by a return have no causal link back to the scan - Lost item fee refunds cannot be traced to the return event that caused them - Plugins (e.g. Rapido ILL) have to reconstruct context from side effects Depends on bug 41728 (checkin availability). Blocks bug 24401 (checkin REST API endpoint). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24401 [Bug 24401] REST API: Check-in https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41728 [Bug 41728] Add `Koha::Item::Checkin::Availability` to centralize logic -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 138

[Bug 38003] New: Add a system preference to configure which patrons fields are used for brief info
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '26

13 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38003 Bug ID: 38003 Summary: Add a system preference to configure which patrons fields are used for brief info Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: philip.orr(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In patron accounts, there is always a brief info area at the top left containing the most important patron data (like name, address, category... etc.) It would be nice to be able to configure which patron fields are used for this brief info area. At the moment it is only possible using system preference HidePersonalPatronDetailOnCirculation to hide all personal fields from the brief info area. But some libraries might want to add more info to the area, or remove only some select fields. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1