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

[Bug 27334] New: Add Template Toolkit support to news items
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '25

23 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27334 Bug ID: 27334 Summary: Add Template Toolkit support to news items Change sponsored?: --- Product: Koha Version: master 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be useful if news items could take advantage of template toolkit syntax. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 41037] New: Allow all funds to display by default in Acquisitions
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '25

22 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41037 Bug ID: 41037 Summary: Allow all funds to display by default in Acquisitions Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kkrueger(a)cuyahogalibrary.org QA Contact: testopia(a)bugs.koha-community.org It would be nice if the table for Acquisitions > funds (also Administration > budgets > funds) included the option to default display all funds at once. Our use case is that we have about 35 funds. When only the first 20 funds display, the Period allocated row values only tally those first 20 rows, rather than our total budget, which is confusing to staff. Eliminating the extra clicks to show all in this screen would be a big help. I understand that adding this to the column configuration is one way to do that, but I could not tell you how (not a developer). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 41072] New: Allow changes to the default 'start after' and 'start before' values in /pendingbookings
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '25

22 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41072 Bug ID: 41072 Summary: Allow changes to the default 'start after' and 'start before' values in /pendingbookings Initiative type: --- Sponsorship --- status: 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: hdunne-howrie(a)westminster.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com We would like to see an option similar to HoldsToPullStartDate but for Bookings so that we can edit the default start after and start before dates in circ/pendingbookings.pl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 28011] New: Add CLI script to update bibs from linked authority records
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '25

22 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28011 Bug ID: 28011 Summary: Add CLI script to update bibs from linked authority records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The script link_bibs_to_authorities.pl will link bibs to authorities, but it won't update the bibs with the data from the authority. I'm proposing adding a new script which will update the bib records from its linked authorities. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 12940] Enter start and end date for course
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '25

22 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12940 Alexander Wagner <alexander.wagner(a)desy.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alexander.wagner(a)desy.de --- Comment #2 from Alexander Wagner <alexander.wagner(a)desy.de> --- If this gets added it would be nice to make it optional as we actually miss-use course reserves for temporary locations that do not run out (new items shelf e.g.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 37918] New: Properly encode email subjects in mailto: links
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '25

22 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37918 Bug ID: 37918 Summary: Properly encode email subjects in mailto: links Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org There are some places in Koha where we use mailto: links with a subject line. An example is the email link added by bug 36595. I believe we need to take a closer look at making sure we are encoding the subject line correctly. Also need to make sure to not include untranslatable and therefore hardcoded bits into the subject messages. -- You are receiving this mail because: You are watching all bug changes.

1 37

[Bug 40313] New: Legacy/migrated categorycode can break patron save
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '25

22 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40313 Bug ID: 40313 Summary: Legacy/migrated categorycode can break patron save Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This should be quite an edge case, but if you have done a data migration and have category codes like "(ABC123", you may notice that you cannot edit your patrons. Due to some suboptimal Javascript, the "(" gets erroneously interpreted by jQuery and leads to an error which breaks other Javascript and prevents the page save from working. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 33222] New: Checkin message does not display when book is overdue and borrower has manual restriction
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '25

22 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33222 Bug ID: 33222 Summary: Checkin message does not display when book is overdue and borrower has manual restriction Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: janet.mcgowan(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Overview: When a borrower with a manual restriction returns an overdue item the returns.pl page displays the checked in items table showing the summary of returned items but there is no Check in message displayed indicating that the borrower has a restriction. If the same restricted patron returns an item that is not overdue you see the Check in message indicating "Reminder: Patron has an indefinite restriction." (or Reminder: Patron was earlier restricted until 31/03/2023. - if the patron is restricted to a specific date). Steps to Reproduce: User has 1 overdue item (I used special due date to set to date in the past) and 1 item that is not overdue. Create a restriction on the patron record - e.g. indefinite restriction. Return the item that is not overdue - Checkin message shows "Reminder: Patron has an indefinite restriction." Return the item that is overdue - no Checkin message displays. Expected results: the Checkin message showing that a patron is restricted should display when returning an overdue book. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 28862] New: Add suffix to name field
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '25

22 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28862 Bug ID: 28862 Summary: Add suffix to name field 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: rcoert(a)arlingtonva.us QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Requesting the addition to the name field for suffix entries (Jr., Sr. III, etc.). Ideally it would be a drop-down box that could be prepopulated (auth_value?) with common entries; allowing for cleaner data and easier account viewing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 39913] New: Fully delete patrons when removing due to refused GDPR consent
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '25

21 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39913 Bug ID: 39913 Summary: Fully delete patrons when removing due to refused GDPR consent 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 21336 When cleanup_database deletes patrons based on the PatronRemovalDelay system preference, it sends those patrons to the deleteborrowers table. It seems like it would be more in keeping with user/patron expectations to fully delete those borrowers, skipping deletedborrowers entirely. We're looking at developing a feature for recovering borrowers from deletedborrowers, and we definitely would not want to allow restoration of patrons who declined GDPR consent. That'd be easier to avoid if we just delete them entirely in the first place. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21336 [Bug 21336] GDPR: Handle unsubscribe requests automatically by optional (administrative) lock, anonymize and remove -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1