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

[Bug 42862] New: bookingsModalDatePicker_spec.ts is failing
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42862 Bug ID: 42862 Summary: bookingsModalDatePicker_spec.ts is failing Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The file bookingsModalDatePicker_spec.ts has a test that checks a booking calendar using hardcoded June 2026 dates, faking "today" as 2026-06-01 so those dates look like the future. That fake date is lost when the test reloads the page midway through, so the real date takes over causing it to fail. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 42912] New: Javascript error on opac-readingrecord when no Circulation history
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42912 Bug ID: 42912 Summary: Javascript error on opac-readingrecord when no Circulation history Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: bibliothek(a)th-wildau.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 42721] New: Update OPACAuthorIdentifiersAndInformation description and labels shown in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42721 Bug ID: 42721 Summary: Update OPACAuthorIdentifiersAndInformation description and labels shown in the OPAC Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org The valid codes in the note for the OPACAuthorIdentifiersAndInformation are not listed in alphabetical order: NOTE: Identifiers for authors and contributors - valid codes to use in the source subfield (024$2) are currently: isni (ISNI), orcid (ORCID), scopus (ScopusID), loop (Loop ID), rid (Publons ID), uri (URI), viaf (VIAF ID), and wikidata (WIKIDATA ID). In addition, the name shown in the OPAC for some of the identifiers need updating: 1. ScopusID --> Scopus ID 2. WIKIDATA ID --> Wikidata ID A Scopus ID normal has a space, for example: https://www.scopus.com/authid/detail.uri?authorId=57221714177 WIKIDATA is not an abbreviation, so I think it should be shown in sentence case as Wikidata. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 41946] New: Superlibrarian should be able to set protected status on patron creation
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41946 Bug ID: 41946 Summary: Superlibrarian should be able to set protected status on patron creation Initiative type: --- Sponsorship --- status: 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Since bug 36085, the protected flag in a patron account was removed from the patron creation form, regardless of if the user is a superlibrarian. 1. With a superlibrarian account, go to Patrons > New patron > Choose any category --> Before bug 36085 : In "Library management" section, there is a Protected yes/no field --> After bug 36085 : the Protected option is no longer there. If I create a SIP account, I now have to create the account, then go back an edit it to add the protection. Non-superlibrarians should still not be able to set the flag on creation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 37707] New: Lead/Trail times should work in combination
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37707 Bug ID: 37707 Summary: Lead/Trail times should work in combination Change sponsored?: --- Product: Koha Version: Main 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: 34440 Whilst working on the lead/trail time addition to bookings we discussed how they should affect things. In the end we decided that they should work in combination when placing bookings so the window of unbookable time before a bookings should be the previous bookings 'trail' period + the current bookings 'lead' period. I've run out of capacity to make that change in the aforementioned bug, so I'm splitting it out here to work on that as a expedient follow-up. Lets get the core functionality in and then continue to polish it. A- | TA >|< LB | -B- | TB >|< LC | -C Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34440 [Bug 34440] Add warm-up and cool-down periods to bookings -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 113

[Bug 21821] New: We should bundle and up to date RangeMessage.xml for Business::ISBN
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21821 Bug ID: 21821 Summary: We should bundle and up to date RangeMessage.xml for Business::ISBN 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Business::ISBN::Data isn't especially maintained and suggests using an up to date RangeMessage.xml file from https://www.isbn-international.org/range_file_generation. We should bundle a more up to date RangeMessage file with koha and set the appropriate environment in both plack and apache to point to the bundled version. This would help with new ISBN's that are not yet in the shipped Business::ISBN::Data package. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 41996] New: Further improvements to EDIFACT error recording
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41996 Bug ID: 41996 Summary: Further improvements to EDIFACT error recording Initiative type: --- Sponsorship --- status: 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: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Depends on: 38689 We've been running the updated edifact error handling code in production for a little while now and there's a few improvements we can make to further enhance and clarify the error reporting for debugging EDI flows. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38689 [Bug 38689] EDIFACT errors should log to a staff accessible location -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 42126] New: t/db_dependent/00-strict.t not testing all perl files
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42126 Bug ID: 42126 Summary: t/db_dependent/00-strict.t not testing all perl files Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org First it lists explicitly the directories to process. Obviously it hasn't been kept up-to-date and some are missing (eg.booking). Also Koha is missing (!). Then we should process the files that are in the git repository, and use Koha::Devel::Files to list them. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 42112] New: Add option for prompting for renewal, always renewing, or never renewing borrower when changing category
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42112 Bug ID: 42112 Summary: Add option for prompting for renewal, always renewing, or never renewing borrower when changing category Initiative type: --- Sponsorship --- status: 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: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Bug 32581 - Update dateexpiry on categorycode change introduced extra clicks for libraries that change category codes frequently for administrative reasons. There should be an option to not offer the renewal. Ideally the option could be: Always renew/Ask for Renewal/Never renew I'm not sure if it makes more sense to set as a sys pref or as a "when changing to or away from this category" setting. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 48

[Bug 36254] New: Port default PASSWORD_RESET and STAFF_PASSWORD_RESET notices to Template Toolkit syntax
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '26

29 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36254 Bug ID: 36254 Summary: Port default PASSWORD_RESET and STAFF_PASSWORD_RESET notices to Template Toolkit syntax Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: roadmap_24_05 Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Blocks: 15278 These might require a bit of refactoring. Looking at Recovery.pm, it looks like the subroutine is passing a custom key/value pair for passwordreseturl, so I'm not sure if an equivalent has been added for Template Toolkit syntax yet. Also not sure if there are any security implications to consider? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15278 [Bug 15278] [Omnibus] Port default slips and notices from bespoke syntax to Template Toolkit -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1