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

[Bug 41067] New: Patrons can self-register without mandatory patron attribute completed if it's not editable
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41067 Bug ID: 41067 Summary: Patrons can self-register without mandatory patron attribute completed if it's not editable Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com If an attribute has 'OPAC mandatory' selected but does not have 'Editable in OPAC' checked, the attribute will not appear on the self-registration form. Patrons can still successfully self-register, however. To make this clearer, the description for 'OPAC mandatory' should be updated to remove 'creating or' from 'Check to make this attribute mandatory when creating or editing a patron from the OPAC', *or* a note should be added indicating that 'Editable in OPAC' must also be checked for the attribute to be included on the self-reg form. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 41766] New: Fix POD in search_for_data_inconsistencies.pl
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41766 Bug ID: 41766 Summary: Fix POD in search_for_data_inconsistencies.pl Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz misc/maintenance/search_for_data_inconsistencies.pl has POD that looks like this: =head1 DESCRIPTION Catch data inconsistencies in Koha database * Items with undefined homebranch and/or holdingbranch * Authorities with undefined authtypecodes/authority types * Item types: * if item types are defined at item level (item-level_itypes=specific item), then items.itype must be set else biblioitems.itemtype must be set * Item types defined in items or biblioitems must be defined in the itemtypes table * Invalid MARCXML in bibliographic records * Patrons with invalid category types due to lower and upper age limits * Any date fields in the database (timestamp, datetime, date) set to 0000-00-00 The list is not in POD list syntax, so it is rendered like this: DESCRIPTION Catch data inconsistencies in Koha database * Items with undefined homebranch and/or holdingbranch * Authorities with undefined authtypecodes/authority types * Item types: * if item types are defined at item level (item-level_itypes=specific item), then items.itype must be set else biblioitems.itemtype must be set * Item types defined in items or biblioitems must be defined in the itemtypes table * Invalid MARCXML in bibliographic records * Patrons with invalid category types due to lower and upper age limits * Any date fields in the database (timestamp, datetime, date) set to 0000-00-00 The list should either be indented to render as a sort of "pre formatted text block" or have the proper list syntax with something like "=item *". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 38755] New: search_for_data_inconsistencies.pl: Fix list of inconsistencies
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38755 Bug ID: 38755 Summary: search_for_data_inconsistencies.pl: Fix list of inconsistencies Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz The relevant POD looks like this: ----------------------------------------------------- =head1 DESCRIPTION Catch data inconsistencies in Koha database * Items with undefined homebranch and/or holdingbranch * Authorities with undefined authtypecodes/authority types * Item types: * if item types are defined at item level (item-level_itypes=specific item), then items.itype must be set else biblioitems.itemtype must be set * Item types defined in items or biblioitems must be defined in the itemtypes table * Invalid MARCXML in bibliographic records * Patrons with invalid category types due to lower and upper age limits * Any date fields in the database (timestamp, datetime, date) set to 0000-00-00 =cut ----------------------------------------------------- perldoc renders the list as running text, which is kind of hard to read. The list should either be formatted with "=item" or indented to be treated as "pre formatted" chunk of text. I would vote for the first option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 40588] New: Clarify impact of edit_any_item permission when no library groups are defined
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40588 Bug ID: 40588 Summary: Clarify impact of edit_any_item permission when no library groups are defined Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20256#c342 Per discussion on Bug 20256, the intended behavior is that when no library groups are defined a user with edit_items but not edit_any_item should only be able to edit items with a homebranch matching the user's logged in branch. Koha's doing this successfully, but the permissions and manual aren't clear about what the user should expext. The edit_items permission says: "Edit items (not including items restricted by library group) (edit_items)" The edit_any_item permissions says "Edit any item including items that would otherwise be restricted" The manual says of edit_any_item "This permission grants the ability to edit items belonging to libraries from other library groups." Together, these imply the assumption that item edits are unrestricted *unless* one defines library groups with the "Limit item edits" option set. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 41600] New: javascript-format translation "# of % selected"
by bugzilla-daemon＠bugs.koha-community.org 19 May '26

19 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41600 Bug ID: 41600 Summary: javascript-format translation "# of % selected" Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: translate.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: Igor.A.Sychev(a)mail.ru QA Contact: testopia(a)bugs.koha-community.org How do I make a translate? English # of % selected Russian # из % выбранных koha-tmpl/intranet-tmpl/prog/js/categories.js:127 koha-tmpl/intranet-tmpl/prog/js/ill-list-table.js:653 https://translate.koha-community.org/translate/koha/25-11/messages-js/ru/?c… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 40935] New: Terminology: Biblio was already issued
by bugzilla-daemon＠bugs.koha-community.org 17 May '26

17 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40935 Bug ID: 40935 Summary: Terminology: Biblio was already issued Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: anneli.osterman(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com koha-tmpl/intranet-tmpl/prog/en/includes/action-logs.inc:233 Biblio was already issued According to Koha's Terminology the word "biblio" should not be used. Use "bibliographic record". Is the word bibliographic record correct in this context? Should it be item? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 41350] New: Terminology: Biblio was already issued
by bugzilla-daemon＠bugs.koha-community.org 17 May '26

17 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41350 Bug ID: 41350 Summary: Terminology: Biblio was already issued Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Keywords: Academy 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 Biblio was already issued koha-tmpl/intranet-tmpl/prog/en/includes/action-logs.inc:239 Biblio should be replaced with bibliographic record. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 31791] New: Add the ability to lock records to prevent modification through the Koha staff interface(s).
by bugzilla-daemon＠bugs.koha-community.org 15 May '26

15 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31791 Bug ID: 31791 Summary: Add the ability to lock records to prevent modification through the Koha staff interface(s). Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl - Add a read-only field - The read-only field will only be editable by superlibrarian - Koha can update these internally for related routines -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 124

[Bug 39318] New: Add hold history for records
by bugzilla-daemon＠bugs.koha-community.org 15 May '26

15 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39318 Bug ID: 39318 Summary: Add hold history for records Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We already have hold history in the patron file. It would be interesting to have the same for records. A Holds history tab with all the holds that happened on a record, including the cancelled ones with the reason if any. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 20418] New: Remove UpdateTotalIssuesOnCirc and make it cron everywhere
by bugzilla-daemon＠bugs.koha-community.org 15 May '26

15 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20418 Bug ID: 20418 Summary: Remove UpdateTotalIssuesOnCirc and make it cron everywhere 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: gaetan.boisson(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I guess the reason this system preference exists it that if you do a lot of circulation, updating this live could have an impact on your server load. But we could make it cron for everyone, it would always work and wouldn't require choices to be made and setup to be done. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4