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

[Bug 41246] New: Deleting patron categories can leave orphaned rules in the overduerules table
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41246 Bug ID: 41246 Summary: Deleting patron categories can leave orphaned rules in the overduerules table Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com To recreate: 1. Add or have a patron category. 2. Go to Tools > Overdue notice/status triggers 3. Set some rules for that category. 4. Delete the patron category 5. Now do "select distinct categorycode from overduerules;" 6. The rule remains with a non-existent categorycode -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 41063] New: Additional fields are broken in Vue
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41063 Bug ID: 41063 Summary: Additional fields are broken in Vue Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: matt.blenkinsop(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, pedro.amorim(a)openfifth.co.uk To reproduce: 1) Go to Administration > Additional fields and add an additional field for erm_agreements 2) Enable ERM and navigate to ERM > Agreements 3) Click to add a new agreement and then fill out the form, making sure to add something into your new additional field 4) Hit save and navigate to the agreement you have just added 5) There will be no additional field added -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 37622] New: Error in erm module when editing an agreement, a license, a package or a titles
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37622 Bug ID: 37622 Summary: Error in erm module when editing an agreement, a license, a package or a titles Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Error in erm module when editing an agreement, a license, a package or a title To reproduce 1- Enable the ERMModule system preference 1- Go to Administration > System Preferences 2- Search for ERMModule 3- Change the value to "Enable" 4- Click on "Save all e-resource management preferences" 5- Return to the main screen 1- Create an agreement 1- Go to e-resource management 2- Click on "Agreements" 3- Click on "New agreement" 4- Fill out the form (mandatory fields) - Agreement name: Natural Medicines - Status: Active 5- Click on "Submit" 2- Edit the agreement 1- Click on "Agreements" 2- Click on "Edit" to the right of the Natural Medicines agreement 3- Click on "Submit" --> Something went wrong: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data We got the same error when editing a license, a package or a title -- You are receiving this mail because: You are watching all bug changes.

1 42

[Bug 38446] New: Permission error for additional fields
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38446 Bug ID: 38446 Summary: Permission error for additional fields Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: michaela.sieber(a)kit.edu QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com With a "normal" libarian account (not superlibrarian) it is not possible to see or edit additional fields in erm . The error message "Something went wrong: Error: Authorization failure. Missing required permission(s)." appears. The patron would need the manage_additional_fields permissions, otherwise the API blocks the request. But the manage_additional_fields permissions should not be necessary as it is for administation. To recreate: 1. Log in as superlibrarian 2. Activate ERM 3. Add a new additional field for Licences under cgi-bin/koha/admin/additional-fields.pl 4. Go to ERM Module 5. Add a Licence and use the new additional field 6. Search for a user, for example borrowernumber=17 7. Give permissions for erm , acquisition and catalogue (staff access) 8. Log in with this account 9. Go to ERM Module 10. Try to edit the licence with the additional field you have created in step 5 Check that the error message mentioned above appears -- You are receiving this mail because: You are watching all bug changes.

1 49

[Bug 29734] New: [OMNIBUS] Recalls for Koha
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29734 Bug ID: 29734 Summary: [OMNIBUS] Recalls for Koha Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Parent bug report for recalls -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 37889] New: Item search: collection search doesn’t work correctly when searching 'collection is not'
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37889 Bug ID: 37889 Summary: Item search: collection search doesn’t work correctly when searching 'collection is not' Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: kati.sillgren(a)porvoo.fi QA Contact: testopia(a)bugs.koha-community.org itemsearch.pl Item search and searching 'collection is not' does not take into account items that do not have a collection code. Not all items have a collection code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 38019] New: Bookings - Have a calendar page with all of the bookings
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38019 Bug ID: 38019 Summary: Bookings - Have a calendar page with all of the bookings 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: koha(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 172014 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=172014&action=e… multiple items booked for one patron Hi, bare with me it's a long one :) We want to submit an enhancement for Bookings. Here at Collecto, we have an "in house" development created by InLibro that we call set aside. The idea is the same as to what bookings offers, but one main difference is that with our set asides, we have a page, accessible from the Circulation module, that presents a interactive calendar. You can use the calendar to choose a day and a time and clic on the period to place the "booking". On the record's page, a button is shown to set aside the document, but Koha returns us to the calendar page. On this page, a list of all the bookable items is shown, so we can choose the right items for the booking. The items are identified as bookable by a subfield M added to the 952 field. If that field is added, the item is shown in the list on the set aside page. >From the set aside page, we are also able to book multiple items for a single patron. (see attachment -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 29677] New: SErials logs
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29677 Bug ID: 29677 Summary: SErials logs 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: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org Serials logs should include more data, now there is no way of knowsing how many issues has been added by subscription or who has added them,all other modules haave detailed info in logs Action_log table should include also modifications on serial table, who, when and action -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 41087] New: EDI Retry: We should add the option to retry EDI processing for errors
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41087 Bug ID: 41087 Summary: EDI Retry: We should add the option to retry EDI processing for errors 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: 39215, 39291 Blocks: 3728 Now that we're catching and reporting EDI processing errors more, we should add the option to retry and revert a message Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3728 [Bug 3728] select mandatory fields broken https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39215 [Bug 39215] EDIFACT quote files should skip orders that cannot be processed rather than failing to complete https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39291 [Bug 39291] Edifact should record an error and move on if there's a problem with transport filename change -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 40616] New: Add option to re-process an edifact message
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '26

06 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40616 Bug ID: 40616 Summary: Add option to re-process an edifact message Change sponsored?: --- Product: Koha Version: 24.11 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)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Sometimes an edifact transport may throw processing errors which are now reported in the UI. It would be nice to have the option of re-running the processing steps for such message if you believe you have corrected the issues (often simple mapping issues for example). The different message types would need slightly different processes to reverse the processing flow to allow for re-processing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5