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

[Bug 8425] Autobarcode generates duplicate barcodes with AcqCreateItems = on order
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '25

24 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8425 --- Comment #33 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Pushed for 25.05! Well done everyone, thank you! -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8425] Autobarcode generates duplicate barcodes with AcqCreateItems = on order
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '25

24 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8425 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)| |25.05.00 released in| | Status|Passed QA |Pushed to main -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38951] New: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38945
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '25

24 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38951 Bug ID: 38951 Summary: https://bugs.koha-community.org/bugzilla3/show_bug.cgi ?id=38945 Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: faizashafique85(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org urdu and arabic books not search via author or specific book name ..kindly this issue plz resolve as soon as possible.. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 35220] New: Merging patrons can cause lock timeouts
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '25

24 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35220 Bug ID: 35220 Summary: Merging patrons can cause lock timeouts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The code to merge patrons uses a transaction to update all of the related patron tables. On systems with a long history (i.e. a big statistics table) this operation can take 30 seconds or more, which begins to cause issues writing to the tables. We need to find a way to speed this up, or to defer the merging of patrons. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 38959] New: Blocked contacts
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '25

23 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38959 Bug ID: 38959 Summary: Blocked contacts 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Should we consider adding a table of blocked or banned email addresses, phone/sms numbers, addresses, etc? Seems like this would be handy. Addresses might be difficult depending on how they are entered. I imagine a table with the ability to enter the reference being banned, and notes, as well as who entered it and a timestamp. I would also envision a way to remove an item if needed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 30088] New: Forgotten password
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '25

23 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30088 Bug ID: 30088 Summary: Forgotten password Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Two thoughts: Is there a reason patrons have to be presented with two fields, one for login or one for e-mail address? The prompt says to enter one or the other. Since there is the possibility for more than one account to have the same e-mail address, should we only ask for the username? The second thought is, should Koha e-mail the account user if a request has been made to reset the password? This seems to be common practice these days. -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 33654] New: Add more permissions to Item Group Cataloging
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '25

23 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33654 Bug ID: 33654 Summary: Add more permissions to Item Group Cataloging 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently, there is only one permission attached to Item Groups: Permission Create, update, and delete item groups, add or remove items from an item group (manage_item_groups) It would be nice to make this functionality more granular within the permissions in Koha. For some catalogers, the permission to add an item to an item group is all they should be able to do in this workflow, but currently, once this overarching item group permission is granted, they can also create groups. Adding permission for only adding items to a group separate from creating groups would be the ultimate goal in this request. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 30070] New: There are performance issues with edifactmsgs when you have a large number of messages
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '25

23 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30070 Bug ID: 30070 Summary: There are performance issues with edifactmsgs when you have a large number of messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client 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 The edifact messages table can grow to a very large size over time, and the page to display them has issues with this growth as it always loads all messages. We should switch this to an ajax driven datatable. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 136

[Bug 38955] New: Support for SIP servers to move reserved items back to queue
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '25

23 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38955 Bug ID: 38955 Summary: Support for SIP servers to move reserved items back to queue Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: hanna.ikonen(a)sivistys.mikkeli.fi QA Contact: testopia(a)bugs.koha-community.org Support is needed for SIP servers to move reserved items loaned to wrong patrons back to the reserved queue. In one location our library uses a self service bookshelf where reservations are kept. Anyone with a library card can open the door, and the bookshelf independently loans the picked up book to the library card which opened it. The problem rises if patron A picks up a reserved item meant for patron B. If it is automatically loaned to patron A, the reserved item stays in waiting -status on patron B's account. After the pick up period is over, patron B will be getting the fee of not picking up a reservation which has not even been on the shelf for them to pick it up. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 38953] New: borrower_message_preferences.borrowernumber should not be DEFAULT NULL
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '25

23 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38953 Bug ID: 38953 Summary: borrower_message_preferences.borrowernumber should not be DEFAULT NULL Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org borrowernumber in borrower_message_preferences is DEFAULT NULL in kohastructure.sql, despite ON DELETE CASCADE in the foreign key. Also borrower message preferences without a borrowernumber don't make any sense. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0