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

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

27 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 --- Comment #677 from Victor Grousset/tuxayo <victor(a)tuxayo.net> --- Comment on attachment 196830 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196830 Bug 10190: DBIC Schema update Review of attachment 196830: --> (https://bugs.koha-community.org/bugzilla3/page.cgi?id=splinter.html&bug=101…) ----------------------------------------------------------------- >From what I can tell there are only auto generated changes in this commit. So it should be marked as "[DO NOT PUSH]" See: https://wiki.koha-community.org/wiki/Database_updates#Files_to_change So the RM will not apply this patch and will regenerate & commit the schema files themselves. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 39732] New: Remove MarcRecordFromNewSuggestion from C4/Suggestions.pm
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39732 Bug ID: 39732 Summary: Remove MarcRecordFromNewSuggestion from C4/Suggestions.pm Change sponsored?: --- 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: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23990 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 41371] New: Title should be recorded to accountlines.description when expired reservation fee is created
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41371 Bug ID: 41371 Summary: Title should be recorded to accountlines.description when expired reservation fee is created Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: anni.maki-mantila(a)turku.fi QA Contact: testopia(a)bugs.koha-community.org Currently when expire_holds.pl cron creates an expired reservation fee, the description in accountlines-table is left blank. If the biblio title would be saved to description field, we could use it in ACCOUNT_PAYMENT and ACCOUNT_WRITEOFF -notices. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 37829] New: Allow additional fields for bookings
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37829 Bug ID: 37829 Summary: Allow additional fields for bookings Change sponsored?: --- 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: paul.derscheid(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Directly from LMSCloud's requirements: > As a Koha library, we want to be able to use configurable additional fields for bookings in order to enable patrons to provide additional information with bookings like the persons who need to be informed when the material is available or a contact person of the institution. > The additional fields will be editable and stored with the booking and should be also available in booking notifications. I think this is interesting because these use-cases seems like a perfect fit for the bookings feature. For example when working with schools or something of the like. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 42472] New: Article requests: patron search does not autocomplete in the staff interface
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42472 Bug ID: 42472 Summary: Article requests: patron search does not autocomplete in the staff interface Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com When the ArticleRequests system preference is enabled, the autocomplete for patron search does not work when placing a request using the staff interface. To reproduce: 1. Enable the ArticleRequests system preference. 2. Go to any record in the staff interface. 3. Click the "Request article" action. 4. Start typing a name in the search patrons search box, for example: mar 5. Note that it does not autocomplete (like when placing holds or checking out items). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 39872] New: Patron club holds - autocomplete does not work
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39872 Bug ID: 39872 Summary: Patron club holds - autocomplete does not work Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When placing a hold for a patron club, the autocomplete for the patron club does not work in the same way that searching for a patron does. The text on the clubs tab says "Enter club ID or partial name". I would expect this to work the same way or similar to the patron autocomplete. What happens instead: 1. If there is only one club that matches, the hold details page is populated with the club details and members. 2. If there is more than one matching club, or you press search without any search text, it lists the available clubs. To replicate: 1. Create a patron club: 1.1 Go to Tools > Patrons and circulation > Patron clubs 1.2 Add a club template: . + New club template . Name: BOOK . Description: Template for book clubs . Save 1.3 Add a club: . + New club > BOOK . Name: SCIFI . Description: Science fiction book club . Save 2. Add a patron to the club: 2.1 Go to a patron's record, for example Mary Burton 2.2 Go to Details > Clubs tab 2.3 Click + Enroll for the SCIFI club 2.4 Click Finish enrollment to complete the enrollment 3. Place a hold for a club: 3.1 Go to any record with items, for example 'The hydrogen sonata' (biblionumber = 333) 3.2 Place a hold: Place hold 3.3 Click the clubs tab 3.4 Note that the instructions say "Enter club ID or partial name" 3.5 Start typing science or sci 3.6 Note that no values are shown, like search for a patron name does on the patrons tab 3.7 Click search 3.8 Since there is only one club, it populates the hold details page and lists the club members 3.9 Note that if you don't type anything and click search, you get a list of all clubs to choose from -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 42473] New: OpacTrustedCheckout: null shown for call number when using OPAC self-checkout
by bugzilla-daemon＠bugs.koha-community.org 26 Apr '26

26 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42473 Bug ID: 42473 Summary: OpacTrustedCheckout: null shown for call number when using OPAC self-checkout Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org If an item doesn't have a call number, the call number value is shown as null when checking out an item using the OPAC self-checkout (with OpacTrustedCheckout system preference enabled). To reproduce: 1. Enable the OpacTrustedCheckout system preference. 2. Add a call number to an item for a record using the staff interface, for example: - Intermediate Perl (biblionumber = 126) - Item barcode: 39999000005134 - Add a call number: 219.325 ABC 3. Go to the OPAC. 4. Click on the Self-checkout link in the header. 5. Enter and submit these barcodes: - 39999000005134 - 39999000011418 6. Note that for Programming Perl, null is shown in the call number column. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 39942] New: Hold found (item is waiting and in transit) is ambiguous
by bugzilla-daemon＠bugs.koha-community.org 25 Apr '26

25 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39942 Bug ID: 39942 Summary: Hold found (item is waiting and in transit) is ambiguous Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: anneli.osterman(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Created attachment 182655 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=182655&action=e… Screenshot of the transfer dialogue When you try to transfer an item that is trapped to a hold and in transfer to another branch (to the pickup location) you will get a dialogue box that says Hold found (item is waiting and in transit) https://gitlab.com/koha-community/Koha/-/blob/main/koha-tmpl/intranet-tmpl/… This is confusing because item/hold cannot be waiting AND in transit at the same time. And the hold is actually not yet waiting in this stage. Should this be changed to a more accurate form? Something like: Hold found (item is in transit to the pickup location) -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 42469] New: Database audit - should be an option to run, instead of running automatically
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '26

24 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42469 Bug ID: 42469 Summary: Database audit - should be an option to run, instead of running automatically Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org For the database audit in the staff interface (More > About Koha > Database audit), there is no option to choose to run it. When you click on the "Database audit" tab in the about section, it automatically runs the database audit. Ideally, you should press a button or be prompted to run it. I'm not sure if there is any impact on performance when running this... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 36039] New: Output of database_audit.pl should be accessible through UI
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '26

24 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36039 Bug ID: 36039 Summary: Output of database_audit.pl should be accessible through UI Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: In Discussion Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: david(a)davidnind.com, dcook(a)prosentient.com.au, katrin.fischer(a)bsz-bw.de, martin.renvoize(a)ptfs-europe.com Depends on: 32693 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32693 [Bug 32693] The 'About Koha' page loads slowly -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61