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

[Bug 39263] New: When an ILL request is closed the item and biblio record created for it should be deleted
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '25

05 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39263 Bug ID: 39263 Summary: When an ILL request is closed the item and biblio record created for it should be deleted Change sponsored?: --- 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: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com When an ILL request is closed (I mean the document has been returned to the supplying library) the item and biblio record created for it should be deleted, either in real time (better I suppose) or with a script in cron They were only created to enable the document to be checked out to the patron. If we don't remove them, they will pollute the catalog. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 29275] New: issuehistory.pl is very slow when there are many historical issues
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '25

05 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29275 Bug ID: 29275 Summary: issuehistory.pl is very slow when there are many historical issues Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Example: We have a library with a biblio that has 39000ish issues in the history, this page cannot be loaded within the plack/apache timeouts, and users can DOS themselves trying to see it. This is admittedly a very extreme case, but even bibs with fewer issues in the history would probably benefit from this page having better performance. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 78

[Bug 25934] New: RequireStrongPassword should be more complex (password policy complexity)
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '25

05 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25934 Bug ID: 25934 Summary: RequireStrongPassword should be more complex (password policy complexity) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org At the moment, RequireStrongPassword uses a minimum password length (of only 3 characters or the sysperf minPasswordLength) and a static regular expression. Here are a number of improvements: 1. A minimum length of 10 characters that can't be lowered via minPasswordLength 2. Should contain 3 of the following 4 sets (lowercase, uppercase, numbers, special characters) 3. Not be the same as a previously set password 4. Should not include dictionary words or common passwords (This could be challenging to do comprehensively on low spec systems, although one variation of this could be to add a customizable list of passwords to exclude.) 5. Should not be equal to the username -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 39396] New: Select2 drop-downs in batch item modification are empty
by bugzilla-daemon＠bugs.koha-community.org 05 Sep '25

05 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39396 Bug ID: 39396 Summary: Select2 drop-downs in batch item modification are empty Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When attempting to modify items with the Batch Item Modification Tool, all of the select2 drop-downs in the form are coming up empty, with no options to select. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 39859] New: Add ability to schedule a full hold queue rebuild from the staff interface
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '25

04 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39859 Bug ID: 39859 Summary: Add ability to schedule a full hold queue rebuild from the staff interface Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be helpful in some circumstances, such as when changing related preferences, if staff could schedule a full queue rebuild. Examples: -Changes to transport cost matrix -Changes to local holds priority system preference -Changes to staticholdsqueue system preference There are probably other cases when it would be helpful as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 35717] New: Add an ordernumber column to suggestions
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '25

04 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35717 Bug ID: 35717 Summary: Add an ordernumber column to suggestions 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This is bug 28844 reworked with the relationship defined in the reverse way. There can be multiple suggestions for the same title currently (the check for duplicate suggestions includes the suggestedby field in the search, so only a single patron is prevented from requesting the same book twice) While we can order only from a single suggestion, bug 19358 and 31632 seek to allow linking multiple suggestions to an order, I believe we need to define the relationship this way now, to allow for future changes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 51

[Bug 40563] New: Some database column attributes display value instead of description
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '25

04 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40563 Bug ID: 40563 Summary: Some database column attributes display value instead of description Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Preservation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com When creating an attribute in a processing, you can select the attribute type as a database column. This is great, as you can then select fields from the biblio, biblioitems or items table to be displayed in the train's table of items. I noticed that for fields linked to authorised values - Damaged status, Withdrawn, Collection, etc. - what displays in the train's table of items is the value, e.g. '4'. It would be more useful for the description to be displayed, as it is elsewhere in Koha. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 35712] New: Record issue_id in old_reserves for completed holds
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '25

04 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35712 Bug ID: 35712 Summary: Record issue_id in old_reserves for completed holds Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: nick(a)bywatersolutions.com There is not currently a direct data linkage between a filled hold in old_reserves and the checkout that filled it in (old_)issues. It'd be helpful if we could put the issue_id into the old_reserves table to make that explicit. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 34610] New: ProtectSuperlibrarianPrivileges, not ProtectSuperlibrarian
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '25

04 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34610 Bug ID: 34610 Summary: ProtectSuperlibrarianPrivileges, not ProtectSuperlibrarian 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We have a syspref called ProtectSuperlibrarianPrivileges, but a couple of places in the code refer to ProtectSuperlibrarian: $ grep -rn --exclude=*.po "ProtectSuperlibrarian " * koha-tmpl/intranet-tmpl/prog/en/modules/members/member-flags.tt:132: .attr("title", _("The system preference ProtectSuperlibrarian is enabled")) koha-tmpl/intranet-tmpl/prog/nb-NO/modules/members/member-flags.tt:132: .attr("title", _("The system preference ProtectSuperlibrarian is enabled")) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 32749] New: Additional fields: Make searchable and display in result list separate attributes
by bugzilla-daemon＠bugs.koha-community.org 04 Sep '25

04 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32749 Bug ID: 32749 Summary: Additional fields: Make searchable and display in result list separate attributes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com At the moment for some of the additional attributes you can specify that they are searchable. If they are searchabale, they will also show up as a separate column in the result list. When you have a lot of fields you want you want to be searchable, that can make the result list unusable. It would be quite nice if it was possible to configure the display bit separately from the field being searchable. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7