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

[Bug 43187] New: Remove mentions of version 24.05 in the Koha Manual
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '26

29 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43187 Bug ID: 43187 Summary: Remove mentions of version 24.05 in the Koha Manual Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)openfifth.co.uk, david(a)davidnind.com, philip.orr(a)lmscloud.de Target Milestone: --- When we moved to the one manual for all versions, the Documentation team decided the Manual is for Koha versions supported by the community. 24.11 is now the new LTS version; we should remove any mentions of older versions in the Manual. - Remove the 24.05 section from the What's new page. - Search for any mentions of 24.05 in other pages. There will be version notes (new features) and attention notes (existing functionality deprecated or updated). The version notes should be removed. You may need to remove the whole paragraph or section an attention note is part of, if the feature does not work that way / does not exist in 24.05 and later. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 41530] New: item_type vs item_type_id inconsistencies in the API
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '26

29 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41530 Bug ID: 41530 Summary: item_type vs item_type_id inconsistencies in the API Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Bug 41456 highlighted a few inconsistencies in the item_type field naming in the API's. I spotted that boh transfer_limit endpoints are using item_type string/null where I believe it should be item_type_id string/null.. it's should only be item_type if it's an object/null. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 25408] New: CanBookBeReserved should check "opacitemholds" policy
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '26

29 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25408 Bug ID: 25408 Summary: CanBookBeReserved should check "opacitemholds" policy Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com how to reproduce : Set an issuing rule with opacitemholds set to "Force" Make a search and select multiple records Place a hold on those records (using multi-hold records) Verify hold is placed on the record (next item available) where it shouldn't! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 161

[Bug 43186] New: Remove mentions of version 23.11 in the Koha Manual
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '26

28 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43186 Bug ID: 43186 Summary: Remove mentions of version 23.11 in the Koha Manual Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)openfifth.co.uk, david(a)davidnind.com, philip.orr(a)lmscloud.de Target Milestone: --- When we moved to the one manual for all versions, the Documentation team decided the Manual is for Koha versions supported by the community. 24.11 is now the new LTS version; we should remove any mentions of older versions in the Manual. - Remove the 23.11 section from the What's new page. - Search for any mentions of 23.11 in other pages. There will be version notes (new features) and attention notes (existing functionality deprecated or updated). The version notes should be removed. You may need to remove the whole paragraph or section an attention note is part of, if the feature does not work that way / does not exist in 23.11 and later. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 38228] New: Allow libraries to choose which auto renewal errors to report on in auto renew notices
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '26

28 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38228 Bug ID: 38228 Summary: Allow libraries to choose which auto renewal errors to report on in auto renew notices Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Automatic renewal notices can report will report on many errors like 'on_reserve', 'restriction' , 'overdue' , 'auto_too_late' , 'auto_too_much_oweing' , 'too_unseen', 'too_many', etc. You can control which errors are reported on via TT in the notice. It would be nice if their was a simpler way ( system preference ) where libraries could chose which errors get reported on and which are skipped. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 29445] New: Checking replace cover image should actually replace cover image
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '26

28 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29445 Bug ID: 29445 Summary: Checking replace cover image should actually replace cover image Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: estherm(a)sodaspringsid.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To duplicate: In this scenario, the Coce image service pulls the incorrect cover image. 1. System setting AllowMultipleCovers is set to allow and CoceProviders is set to all. 2. Upload a new image cover and select replace cover image. 3. Check the normal view in the staff client and see that the new image displays as the default image and the Coce image displays as a second hidden image that can be selected to view. 4. Check OPAC view, both images continue to be displayed. Repeat these steps but set AllowMultipleCovers to not allow. Both images continue to be displayed. I would have expected that by checking replace cover image that the cover image is actually replaced. Instead it looks like ticking that box sort of makes the image the first image that is displayed but doesn't actually replace. As for the setting AllowMultiple Covers - this needs clarification. Ideally a bib record should allow multiple images but with the option to select the default cover image and the ability to not show the Coce image if it is not correct. This may be related to ticket 29359 and 26933. It looks like additional cover image tools or preferences are needed. Selecting a default image, actually replacing a cover image in place of the Coce image, deleting an image, selecting how many images show, etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 19037] New: Circulation and fine rules test tool
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '26

28 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19037 Bug ID: 19037 Summary: Circulation and fine rules test tool Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Add a test tool for circulation and fine rules. The point of the tool is to display the effective issuing rule that matches item, patron and branch. Add a REST API endpoint to query effective issuing rules by given parameters. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 77

[Bug 39882] New: Add phone number masking option
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '26

28 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39882 Bug ID: 39882 Summary: Add phone number masking option Change sponsored?: --- Product: Koha Version: Main 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice it we should add a mask for phone number fields. For certain things, like Twilio, it is important that a phone number gets set in an exact format. We have Maskito for date entry, we might be able to leverage that for phone numbers: https://maskito.dev/recipes/phone -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 60

[Bug 27834] New: CircControl syspref is used wrong in TooMany function C4::Circulation
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '26

28 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27834 Bug ID: 27834 Summary: CircControl syspref is used wrong in TooMany function C4::Circulation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The CircControl syspref description says > Use the checkout and fines rules of > PickupLibrary: the library you are logged in at. > PatronLibrary: the library the patron is from. > ItemHomeLibrary: the library the item is from. This is mostly true but there is one exception in the TooMany function where it actually doesn't just change which libraries rules are used but how the the calculation is performed. With PatronLibrary set the behaviour is as expected by reading the syspref description. However with the setting PickupLibrary the behaviour changes now, instead of just using the rules of the pickup library we also only take into account the loans in the pickup library when calculating whether we are over the checkout limit or not. The same happens with ItemHomeLibrary where we instead calculate the patron's checkouts in the home library of the item being checked out. We should really try to fix this either by a) showing that ItemHomeLibrary and PickupLibrary is unacceptable and no one actually wants that, that would allow then making the behaviour similar as what it is to PatronLibrary (so just selecting the right circ rule instead of changing calculation method). b) Provide a new syspref for changing the calcutation method when PickupLibrary or ItemHomeLibrary CircControl values are used, and set it on upgrade enabled as default. Ps. svc/letters/preview might use CirControl wrongly as well, I'm not 100% I didn't quite understand but as for other usages of CircControl syspref I grepped where it was used and it correctly only changed the circ rules to be used instead of changing behaviour. So in addition to TooMany we might have to do some changes to svc/letters/preview if it turns out it changes behaviour as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 50

[Bug 40115] New: Extensive acquisition permissions needed to search vendors
by bugzilla-daemon＠bugs.koha-community.org 28 Oct '26

28 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40115 Bug ID: 40115 Summary: Extensive acquisition permissions needed to search vendors Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: christian.nelson(a)uwasa.fi QA Contact: testopia(a)bugs.koha-community.org In the acquitions module (acqui-home.pl) when searching for vendors (eg. for receiving orders) the user gets the message "Something went wrong: Error: Authorization failure. Missing required permission(s)." and the page stays on loading forever. This happens unless the user has extensive acquisition permissions, such as managing budget plannings (planning_manage). It should be possible to perform routine acquitions tasks such as creating baskets and receiving orders without permissions to modify budgets. Koha version: 25.05.00.000 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4