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

[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 24260] New: REST Self Registration
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '25

21 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24260 Bug ID: 24260 Summary: REST Self Registration Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi Support self registration via REST API -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 30299] New: Create a Registration API to allow for use of email verification when outside systems are registering patrons
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '25

21 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30299 Bug ID: 30299 Summary: Create a Registration API to allow for use of email verification when outside systems are registering patrons Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com CC: tomascohen(a)gmail.com Some discovery systems (Aspen for instance) provide a self registration function. Currently the Koha preference 'PatronSelfRegistrationVerifyByEmail' cannot be utilized via the API. We propose to add two endpoints: 1 - Registration - This will take a borrower object, verify the required/unwanted fields, and create a patron modification request as on 'opac-memberentry.pl' when verification is enabled - The endpoint will take an option to send/suppress the email from Koha so that integrating systems may generate their own - The endpoint will take an optional return URL to be passed through when generating the verification email so the outside system can handle the verification - The endpoint will return the verification token 2 - Verification - The endpoint will accept the token generated above and complete patron creation as in opac-registration-verify.pl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 33703] New: Bug in Date of Birth Field Entry
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '25

21 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33703 Bug ID: 33703 Summary: Bug in Date of Birth Field Entry 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: kkrueger(a)cuyahogalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 150894 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=150894&action=e… DateNoSlash_1 Description: When using the Koha Date of Birth field to add a new patron, entering a date without punctuation (/ or -) causes the date to change to an incorrect date. Steps to reproduce: 1. From Koha Patron module > add new patron > patron identity section, Date of birth field, enter a birthdate for 24 May 1964 as 05241964 (DateNoSlash_1.png) manually. 2. Tab or hit enter, and the birth date that is recorded changes to 06/10/1964 or June 10 1964 (DateNoSlash_2.png). Similar behavior happens whenever the date is entered without punctuation. Expected Results: If data is entered in this field without slashes or hyphens, the slashes would be input without changing the intended date. Suggesting here a correction to correctly assign birthdates as entered with or without punctuation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 120

[Bug 16207] New: Incorporate circulation and fine rules for library groups
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '25

20 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16207 Bug ID: 16207 Summary: Incorporate circulation and fine rules for library groups Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I think we could simplify circulation and fine rules by incorporating library groups into the mix. For example, I have 27 libraries, and 8 of them follow the same set of rules that are different from the defaults. So, what if instead of cloning these special rules to 8 different libraries (and who knows how many other duplicated sets of rules there are), we defined a set of rules for a library group. If the library is part of that group, it goes by those rules. I don't know if we want to use the same library groups that are already defined in the libraries and groups, or if we want to create a unique Circ rule group. Because, there is always the chance that one or more of the libraries in the 8 that are grouped together by affiliation or region could have a slightly different set of rules. However, I think rules by groups would make managing rules far less complicated than managing groups of cloned rules. Christopher -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 18327] New: Reception date when receiving multiple issues for a subscription is not the good one
by bugzilla-daemon＠bugs.koha-community.org 20 Oct '25

20 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18327 Bug ID: 18327 Summary: Reception date when receiving multiple issues for a subscription is not the good one Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When receiving several issues for a subscription (Serials > Serial collection > Multi receiving), the reception date is identical to the publication date instead of being the today date. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 35654] New: Add option to delete last item to delete_items.pl
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '25

17 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35654 Bug ID: 35654 Summary: Add option to delete last item to delete_items.pl 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: enica(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Apologies if there's a duplicate bug. It would be great to add a parameter to delete_items.pl to delete the record if the last item getting deleted is the only one that remains. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 52

[Bug 33737] New: Add bookings to patron details
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '25

17 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33737 Bug ID: 33737 Summary: Add bookings to patron details 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com, testopia(a)bugs.koha-community.org Depends on: 29002 As part of the bookings workflow, we should add a "bookings" tab to the patron details page. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29002 [Bug 29002] Add ability to book items ahead of time -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 57

[Bug 35946] New: If an item has future bookings on it and it is marked as lost we should highlight this to the librarian
by bugzilla-daemon＠bugs.koha-community.org 17 Oct '25

17 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35946 Bug ID: 35946 Summary: If an item has future bookings on it and it is marked as lost we should highlight this to the librarian 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 29002 If an item is made unavailable for bookings for some reason, we need to highlight to the end user that there are bookings outstanding against the item and that they'll need to resolve this somehow.. probably by assigning an alternate item to the booking or cancelling the booking and notifying the patron. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29002 [Bug 29002] Add ability to book items ahead of time -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9