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

[Bug 41834] New: Remove systempreferences's options, explanation and type DB values
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '26

19 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41834 Bug ID: 41834 Summary: Remove systempreferences's options, explanation and type DB values Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 41833 We currently have to set options, explanation and type in sysprefs.sql and the atomic/dbrev files. However we (almost) never use them, we rely on the values in the yml files. We could remove them and don't require them when when add new sysprefs. It will avoid the mess we currently have (mismatch between new and updated installations, see bug 41682 and bug 41800). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41833 [Bug 41833] Use YML description for syspref's search -- You are receiving this mail because: You are watching all bug changes.

1 64

[Bug 23756] New: Appendix for workflows
by bugzilla-daemon＠bugs.koha-community.org 19 Aug '26

19 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23756 Bug ID: 23756 Summary: Appendix for workflows Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Wondering if the documentation should include workflow examples for different tasks. I know how different each library can be with their workflows, but workflows seem to be a common topic, and there are multiple ways to approach different tasks. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 36369] New: Make APIClient be more useful
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '26

18 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36369 Bug ID: 36369 Summary: Make APIClient be more useful 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org I file this report for discussion. In my opinion, there's too much duplicated code on the API client libraries. And the APIClient "class" is just a shortcut to avoid instantiating the module-specific API clients: ```javascript import ERMAPIClient from "./erm-api-client"; ... export const APIClient = { erm: new ERMAPIClient(), ``` Then used everywhere like this: ```javascript import { APIClient } from "../../fetch/api-client.js" ... const client = APIClient.erm await client.agreements.count().then( ``` IMHO, we need a real APIClient class that would implement generic methods like: ```javascript create: params => this.post({ endpoint: params.endpoint ? params.endpoint : "/", body: params.resource, headers: params.headers }), ... getAll: params => this.get({ endpoint: params.endpoint ? params.endpoint : "/", params.query, headers: params.headers, }), ... count: params => this.count({ endpoint: params.endpoint ? params.endpoint : "/", "?" + new URLSearchParams({ _page: 1, _per_page: 1, ...(params.query && { q: JSON.stringify(params.query) }), }), }), ``` and the API Client classes (like ERMAPIClient) should inherit from it, somehow. For doing so, we will face another design roadblock: While I uderstand that ERMAPIClient is a single place to have all the ERM module-needed API actions, it still feels weird from an OOP perspective how things are organized. I feel like we should have individual classes, like: ```javascript export RecordSourcesAPIClient extends APIClient ``` and then have a new type of class along this lines: ```javascript import CitiesAPIClient from "./cities-api-client"; import RecordSourcesAPIClient from "./record-sources-api-client"; ... export const AdminAPIClient = { cities: new CitiesAPIClient(), record_sources: new RecordSourcesAPIClient(), ... }; ``` this way, we will avoid repeating ourselves (less bugs!) and the code is (I expect) more reusable. I also think the `embed` handling should just be a list for the different methods, like: embed: [ 'patron', 'patron.category' ] and generically handled by APIClient. No need to build the headers manually everywhere. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 59

[Bug 41626] New: Add Koha::CSV::Reports for report exports
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '26

18 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41626 Bug ID: 41626 Summary: Add Koha::CSV::Reports for report exports Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 41619 Blocks: 41621 This bug adds Koha::CSV::Reports to standardize CSV generation for report exports. Files to update: - reports/guided_reports.pl - misc/cronjobs/runreport.pl Benefits: - Consistent CSV formatting across all report exports - Proper quote handling for Excel - Testable code Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41619 [Bug 41619] Add `Koha::CSV` https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41621 [Bug 41621] Use Koha::CSV everywhere [UMBRELLA] -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 42064] New: Add ability to specify a default value for patron attributes by category
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '26

18 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42064 Bug ID: 42064 Summary: Add ability to specify a default value for patron attributes by category Initiative type: --- Sponsorship --- status: 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: michael.adamyk(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Some libraries use patron attributes to track statistics that are always the same for some of their patron categories, but other categories need the ability to select from a list of attributes. I don't know how difficult this would be, but one option might be for under patron attribute settings, have a dynamic display that would list all patron attributes that are available for patrons of this category. For each it would have either a free text field (for uncontrolled attributes) or a dropdown (if controlled by an authorised value) that would allow entering a default for this patron category only. Likely would depend on either bug 22730 or 20682, though I'd need a developer to confirm that. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 37596] New: Pending on-site checkouts terminology change needed
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '26

18 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37596 Bug ID: 37596 Summary: Pending on-site checkouts terminology change needed 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: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To replicate: 1. Enable OnSitecheckouts 2. Find some items and check them out by checking the box for On-Site. 3. Go to circulation and select the button for Pending On-site Checkouts 4. See a table of checked-out items The table found in Pending On-site Checkouts is not populated until items are actually checked out. The term Pending is confusing because the items are not in a waiting status. Pending should be changed to Current or Outstanding. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 23258] New: Batch holding
by bugzilla-daemon＠bugs.koha-community.org 18 Aug '26

18 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23258 Bug ID: 23258 Summary: Batch holding Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Add a "batch holding" tool (just like batch item modification, batch patron deletion...) This tool would allow to place or cancel holds in batch. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 53

[Bug 28085] New: Add "Forget" link for search to hold feature to detail page
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '26

17 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28085 Bug ID: 28085 Summary: Add "Forget" link for search to hold feature to detail page 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When using the "Search to hold" feature from the patron account, there is an option on the result page to "forget" the current selected user. We should also have this link on the hold pull down on the catalog detail page. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 32980] New: Checkouts for guarantees are not shown if patron also has a guarantor
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '26

17 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32980 Bug ID: 32980 Summary: Checkouts for guarantees are not shown if patron also has a guarantor Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Circulation Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Steps to reproduce: 1. Create a patron category of type 'Professional' (or any type that allows guarantors) 2. Create 3 patrons in this category. Let's call them A, B, and C 3. Do at least one checkout for A and at least one for C 4. Make B the guarantor of C 5. Go to B details page. You should see the checkouts of C in the "Relatives' checkouts" tab 6. Go to B checkout page. You should see the checkouts of C in the "Relatives' checkouts" tab 7. Make A the guarantor of B 8. Go to B details page. Now you should see the checkouts of A in the "Relatives' checkouts" tab but not the checkouts of C (KO) 9. Go to B checkout page. Now you should only the checkouts of A in the "Relatives' checkouts" tab but not the checkouts of C (KO) -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 23356] New: IndependentBranches: overdues list
by bugzilla-daemon＠bugs.koha-community.org 17 Aug '26

17 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23356 Bug ID: 23356 Summary: IndependentBranches: overdues list 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: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If syssprefs "IndependentBranches" and "IndependentBranchesPatronModifications" is used, list of overdues (/cgi-bin/koha/circ/overdue.pl) should be limited only to current library as "Library of the patron". Now local staff can see anonymised but complete list overdues. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7