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

[Bug 30144] New: Add support for EDI GIR:LVT, Servicing instructions, segment
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30144 Bug ID: 30144 Summary: Add support for EDI GIR:LVT, Servicing instructions, segment 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We allow for free text instructions in the EDI FTX segment now, taken from the vendor notes field. But this is at the order level, it would be helpful to add support for the LVT segment at the line level. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 123

[Bug 39658] New: Allow definition of non-hierarchical linked patron accounts
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39658 Bug ID: 39658 Summary: Allow definition of non-hierarchical linked patron accounts Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In a Koha system containing multiple functionally-autonomous libraries, one patron may have multiple distinct accounts within the same Koha system. These accounts represent distinct cards from distinct libraries and need their circulation rules enforced as such, so they can't be merged into one account. But no one of these accounts is "primary" and they all represent the same person, so guarantor/guarantee relationships are a poor conceptual fit (and may already be in use for their intended purpose). These linked/shared accounts would: - clearly link between each other in the Details of the patron record - optionally reciprocally enforce restrictions and blocks due to fines & fees (when one account is blocked, all are) - optionally allow checkout of on-hold items for shared accounts For that last item, assuming one patron has accounts card1 and card2. They have a hold ready for pickup on their card1 account. If Koha attempts to check the waiting item out to the card2 account, koha should check the item out on the card1 account, mark the hold complete, and give the user a clear on-screen message as to what happened. It should not ask for confirmation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 168

[Bug 42344] New: Remove CircSidebar
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42344 Bug ID: 42344 Summary: Remove CircSidebar Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 42330, 16530, 31403 Now that we can collapse the sidebar on all views (see bug 42330) we can remove the pref CircSidebar. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16530 [Bug 16530] Add a circ sidebar navigation menu https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31403 [Bug 31403] Activate circulation sidebar (CircSidebar system preference) on default in new installations https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42330 [Bug 42330] Use main-container.inc from all the templates -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 7340] Only send HOLD_PLACED if item is available and hold was patron initiated
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7340 --- Comment #3 from Koha collecto <koha(a)collecto.ca> --- It would be very interesting. Some libraries asking for this option. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 --- Comment #959 from Chloé Zermatten <chloe.zermatten(a)openfifth.co.uk> --- (In reply to Jonathan Druart from comment #958) > (In reply to Chloé Zermatten from comment #955) > > 2: logged_in_user is not available to circulation triggers as it stands. I > > could make it available, but it also is a lot more data than what > > circulation triggers really needs. That said we do need to move from > > consulting the logged in library to looking for the logged in user’s home > > library instead - and that much is fixed (see commit message). > > Indeed, I thought we had it widely available. > > > 5: The comment between those two lines reads “It may still be present in > > DBs that pre-date the atomic update.” I don’t know if you’ve seen it (won’t > > come up if grepping I don't think?). Does that answer it? I can ask Martin > > about it otherwise. > > It does not make sense to me. If we run the test on this version of the > code, the permission shouldn't be in the DB. > Ha, btw, the db_rev is not idempotent. > > > 10: best practice: I don’t think so - but I do think it’s a step in that > > direction (the direction of travel so far had been to remove duplicate code, > > prevent redundant data (re)loads, remove duplicated logic, etc). Further > > refactoring into more specialised components will be beneficial. 39756 (long > > overdue cron) can certainly take that refactoring further. > > I don't understand why we have most of those functions in "store". They > don't touch the store state. They could certainly be moved to a plain JS > module, that could be easily unit-tested without Pinia/Vue at all. Note that > I am not requiring unit tests, but only flagging what seems to be a > problematic pattern. OTOH that does not seem to be a trivial refactoring... Re-db_rev: noted - I can look at that later today, but more likely tomorrow. Re-extracting methods that do not touch store state out of store: agreed on the plain JS module option, especially from a future testability standpoint. I think the best way to figure out exactly how non-trivial this is is for me to actually have a crack at it, which I can spend some time on tomorrow. I can either add it in as a further commit on here or raise it as follow up bug (which would be a 39756 dependency) - do let me know if you have a preference! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7340] Only send HOLD_PLACED if item is available and hold was patron initiated
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

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

1 0

[Bug 7340] Only send HOLD_PLACED if item is available and hold was patron initiated
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

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

1 0

[Bug 37471] New: Add permissions for managing Catalog Concerns
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37471 Bug ID: 37471 Summary: Add permissions for managing Catalog Concerns Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kkrueger(a)cuyahogalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Similar to bug 33363 for purchase suggestions, it would be great if there were more specific permissions for catalog concerns. It would be nice if the ability to manage these were limited to those with assigned permissions on the catalog staff. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 42980] New: ILL Batches: Have a 'select for all' option when using AutoILLBackendPriority
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42980 Bug ID: 42980 Summary: ILL Batches: Have a 'select for all' option when using AutoILLBackendPriority Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com Target Milestone: --- -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 43158] New: Add clear button (x) to search input fields
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '26

14 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43158 Bug ID: 43158 Summary: Add clear button (x) to search input fields Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Add a clear/reset button (x icon) on the search input fields that appears when text has been typed, allowing users to quickly clear the search box without manually selecting and deleting the text. Start with the OPAC search input, then extend to the staff interface. This is a common UX pattern in modern web applications (browsers natively support it for type=search inputs, but Koha uses type=text). Implementation options: - Use HTML5 type=search which provides a native clear button in most browsers - Or add a positioned x icon via CSS/JS that clears the input on click The native type=search approach is simpler and more accessible. -- You are receiving this mail because: You are watching all bug changes.

1 13