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

[Bug 18823] New: Advanced editor - Rancor - add ability to edit records in import batches
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18823 Bug ID: 18823 Summary: Advanced editor - Rancor - add ability to edit records in import batches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl These patches allow the use of import batches as targets in the advanced editor -- You are receiving this mail because: You are watching all bug changes.

1 228

[Bug 27648] New: Add itemnumber as an option for moving/attaching an item from one bib to another
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27648 Bug ID: 27648 Summary: Add itemnumber as an option for moving/attaching an item from one bib to another Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When moving an item or order to another bib you must enter the barcode of the item in "attach item." We have found this to be problematic for some items because they are ones that are still on order so they don't have barcodes yet. This means we have to add a barcode to the item record in order to move it. It could be for something we haven't even received yet so we have to add it in order to move it and then delete the barcode because when we do receive it there will be a different barcode attached to it by the vendor. It would be very helpful if we could also use the itemnumber as a way to move the item. It already exists and would be a much more efficient way of performing this function. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 37251] New: Default values should be applied when cataloging using the advanced cataloging editor (rancor)
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37251 Bug ID: 37251 Summary: Default values should be applied when cataloging using the advanced cataloging editor (rancor) 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 36272] New: Exporting too many items from item search to barcode file gives "Request-URI Too Long"
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36272 Bug ID: 36272 Summary: Exporting too many items from item search to barcode file gives "Request-URI Too Long" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org To reproduce in KTD: - Login to the staff client - Go to "Item search" - Click on "Search" without adding any limitations - Change to "Show [All] entries" - this should show about 961 items - Click on "Select visible rows" - Click on "Export selected results (961) to" and choose "Barcode file" - This should result in this error: Request-URI Too Long The requested URL's length exceeds the capacity limit for this server. The URL of the page that shows the error looks like this: http://localhost:8081/cgi-bin/koha/catalogue/item-export.pl?format=barcodes… etc etc The solution is probably to do a POST, not a GET? Similar to bug 32278, but in a different area. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 36455] New: Default the hold queue link to your logged in library
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36455 Bug ID: 36455 Summary: Default the hold queue link to your logged in library 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: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reduce clicks for library staff, defaulting the hold queue link on circulation home to the logged in library would be helpful, either as an option or as the default behavior with the option to run it for a different branch from the queue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48

[Bug 38964] New: Fix column span in footer of staff interface account payment page
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38964 Bug ID: 38964 Summary: Fix column span in footer of staff interface account payment page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 33137 The footer of the table of charges on the account payment page has incorrect column spans, resulting in the rows having incorrect alignment. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33137 [Bug 33137] Make sure columns on transactions and 'pay fines' tab are matching up -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 38633] New: Calendar - Weekly closures are ignored when setting a yearly repeating holiday
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38633 Bug ID: 38633 Summary: Calendar - Weekly closures are ignored when setting a yearly repeating holiday Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: jeremy.evans(a)ukhsa.gov.uk QA Contact: testopia(a)bugs.koha-community.org There seems to be an issue in Koha when setting up a yearly repeating holiday in a range. Currently running Koha 23.11.10 I had not noticed this issue in previous versions - we would have been running 22.11 when I last set up a repeating closure range. We set in the calendar a yearly closure period from 20 December to 6 January each year. This year 21/22 December and also 28/29 December are weekends when the library is already closed. However if I look at the 2025 or 2026 calendars, those dates which are weekends in 2024 are showing as open if they are on a weekday in 2025 or 2026. They should be closed as they are still within the date range of the yearly repeating closure. On testing it appears that, if weekly repeatable holidays are set, Koha ignores those days in the holidays on a range (presumably because they are already marked as closed). You can see this clearly because they do not appear in the list of dates on the right. This does become an issue when you are using holidays on a range repeatable yearly. Our temporary workaround was to remove all of the repeating holidays. Then add in the Christmas/ New year closure range and the add back in the weekly Saturday and Sunday closures. It appears to be necessary to set the yearly repeatable holidays on a range first, and to add the weekly repeatable holidays afterwards. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 22415] New: Koha::EDI should not use Log::Log4perl directly
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22415 Bug ID: 22415 Summary: Koha::EDI should not use Log::Log4perl directly 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 Target Milestone: --- We have Koha::Logger for instantiating Log4perl loggers now.. it should be used here too. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 38423] New: EDIFACT invoice files should skip orders that cannot be receipted rather than failing to complete
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38423 Bug ID: 38423 Summary: EDIFACT invoice files should skip orders that cannot be receipted rather than failing to complete Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucy.vaux-harvey(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org When loading an EDIFACT invoice file, if the process finds a problematic order (usually a cancelled order or a deleted bibliographic or item record) the load process gets stuck and displays as 'Processing' in the EDFACT messages page. This usually means that the remainder of the orders in the file have to be manually receipted by library staff as vendors are reluctant to re-process part invoices. It would be preferable if the process could skip, and report any problem orders but complete all other receipts. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 38905] New: API Update an item for a biblio should use edit_items instead edit_catalogue
by bugzilla-daemon＠bugs.koha-community.org 27 Feb '26

27 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38905 Bug ID: 38905 Summary: API Update an item for a biblio should use edit_items instead edit_catalogue Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: michaela.sieber(a)kit.edu QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com For the API https://api.koha-community.org/#tag/biblios/operation/updateBiblioItem a user must have the permission edit_catalogue {"permissions":{"editcatalogue":"edit_catalogue"}} it should be {"permissions":{"editcatalogue":"edit_items"}} -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18