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

[Bug 40154] New: Deleting an item does not warn about an item level hold
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40154 Bug ID: 40154 Summary: Deleting an item does not warn about an item level hold Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: anni.maki-mantila(a)turku.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl At the moment, Koha doesn't give any warning if user is deleting an item that has a hold attached to it. Item is simply deleted and the item level hold vanishes as well. To reproduce: 1. Make an item level hold 2. Delete the item using alternative A or B: A: Open the biblios Detail-view -> From the toolbar, open "Edit"-dropdown menu -> Manage items -> Delete the item that has an item level hold attached to it from "Actions"-dropdown menu B: Open the biblios Detail-view -> Select the item that has an item level hold attached to it -> Click "Delete selected items" -> Confirm deletion 3. Notice that the item is deleted without any warning and the item level hold has disappeared 4. Run following sql report: SELECT * FROM old_reserves WHERE biblionumber = [biblionumber you used in the test] 5. Notice that the item level hold is not found in old_reserves-table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 29497] New: Add ability to link authorities automatically in the advanced editor
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29497 Bug ID: 29497 Summary: Add ability to link authorities automatically in the advanced editor 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 It would be nice to add the link authorities automatically button in the advanced editor. Right now catalogers must use the basic editor in order to use this option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 36393] New: Renewal with a specific date does not take the new date due that we pick
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36393 Bug ID: 36393 Summary: Renewal with a specific date does not take the new date due that we pick 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: hammat.wele(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To reproduce 1- Log in to the staff interface 1-1. Make sure you have a ciculation rule that allows you to renew 1-2. set the AllowRenewalLimitOverride system preference to Allow and SpecifyDueDate to Allow 2. Check out the item to a Borrower 5. Access the borrower's account and renew it until the limit is reached and note the due date. 6. Go to Circulation, click Renew 7. Enter the item barcode and choose a due date further than the due date from step 5 and submit 8. Click on Override limit and renew button ---> Note that the new date due is not the date that we picked in step 7 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 37189] New: Renewals: Koha prioritizes hard due date from circulation rules over manual due date, although the manual due date is earlier
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37189 Bug ID: 37189 Summary: Renewals: Koha prioritizes hard due date from circulation rules over manual due date, although the manual due date is earlier Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: isabel.pineda(a)ds.edu.sv QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I wrote this comment last week in Bug 36393, but I am not sure if this bug is still being attended, so I decided to file a new bug. Please delete it if it is duplicated: After updating from version 23.11 to 24.05, the renewal for a specific date is not working anymore. Although I give a specific date for a specific renewal, the system takes automatically the hard due date from the circulation rules. e.g. In "Administration > Circulation rules" I save "15.08.2024" as hard due date for a specific item type and patron category. Then I go to one patron of the above category to renew his borrowed items, and manually select "30.07.2024" as due date. -> The system renews the items until 15.08.24. It ought to prioritize the manual due date for this specific patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 38116] New: Patrons search description should be built from DT's search settings
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38116 Bug ID: 38116 Summary: Patrons search description should be built from DT's search settings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 38112 We are building a description of the search on top of the patrons search table. But this is not accurate and does not reflect the exact search result that is displayed in the table. This is because column filters can used after we submitted the form (on the left). We could try to build it using DT's search settings, and it would then even be possible to have it for all tables. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38112 [Bug 38112] Description of patrons search no longer displayed -- You are receiving this mail because: You are watching all bug changes.

1 40

[Bug 20958] New: Allow admins to choose data types for additional attributes
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '26

28 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20958 Bug ID: 20958 Summary: Allow admins to choose data types for additional attributes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: hughr(a)brimbank.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently additional patron attributes are always strings. It would be really useful to be able to specify what data type an additional attribute should be when it is created, like you can specify whether it has to be unique, or is repeatable. e.g. we might want it to be a DATE, or possibly a DATETIME, or we may indeed want a STRING, or an INT, or a DECIMAL etc - it really depends on what a given library is using the attributes for, and how they might want to run reports against it. This would be a more holistic way to deal with Bug 6339. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 19336] New: Add option to fines.pl to apply maximal fine amount after delay
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '26

28 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19336 Bug ID: 19336 Summary: Add option to fines.pl to apply maximal fine amount after delay Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.bourgault(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 88

[Bug 40197] New: Datepicker on data provider "Run now" modal not working correctly
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '26

27 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40197 Bug ID: 40197 Summary: Datepicker on data provider "Run now" modal not working correctly Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: clemens.tubach(a)kit.edu, jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, michaela.sieber(a)kit.edu, pedro.amorim(a)openfifth.co.uk Created attachment 183382 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=183382&action=e… Screenshot of "Run now" modal When running a SUSHI/COUNTER API download manually via the "Run now" button, the date picker in the modal has a broken month pull down. To test: - Activate the ERMModule system preference - Add a data provider (you can just make up date for testing this) - After saving, click on the "Run now" button in the result list - Click into the "Begin date" field to open the calendar widget - Click on the month at the top to open the pull down - Confirm it only "flickers" open, but doesn't allow selection This was confirmed in main and 24.11. In 24.11 there is also some weird effect when first selecting the Begin date and the End date after. The first date widget will overlay with the second (see screenshot). This was not consistently reproducible in main. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 20682] New: Authorised values should have an option to set a default
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '26

27 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20682 Bug ID: 20682 Summary: Authorised values should have an option to set a default 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: hughr(a)brimbank.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are many places in Koha where values can be chosen via a drop-down menu listing a particular authorised value. For example SUGGEST_FORMAT is used to populate the list of formats that can be selected when placing a purchase suggestion. Currently these lists appear in alphabetical order by description or OPAC description (depending on context), and the first option in the list is usually auto-selected (i.e. more or less default behaviour for a vanilla HTML <select> element). This is problematic in many circumstances as users will accidentally 'select' the first alphabetical option if they don't change anything. There should be a setting in Authorised Values to set between zero and one values per category to be the default value (probably in authorised_values.pl?op=add_form). This would then add a 'selected' attribute to the <option> tag wherever the authorised value list appears as a dropdown menu. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 36192] New: [OMNIBUS] CSRF Protection for Koha
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '26

27 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36192 Bug ID: 36192 Summary: [OMNIBUS] CSRF Protection for Koha Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 34478 will be pushed soon, this bug will be for tracking remaining work with dependencies etc, more info to follow -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 156