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

[Bug 30274] New: Non-reservable items should only fill item-level reserves
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '25

02 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30274 Bug ID: 30274 Summary: Non-reservable items should only fill item-level reserves Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests 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 For item types where 'holds allowed(total)' equals 0, you can still place reserves on these non-reservable items via the staff client by overriding the circulation rule. The bug is that, when you check in an item that is non-reservable (holds allowed is 0), it will trigger the holds pop-up and can fill a biblio-level hold ("next available"). The holds pop-up should only be triggered by non-reservable items if there is an item-level reserve on it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 37188] New: Batch patron modification from report results broken in 24.05
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '25

02 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37188 Bug ID: 37188 Summary: Batch patron modification from report results broken in 24.05 Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: run a report using borrowernumber as one of the columns. Select batch actions from visible results. See that batch patron modification is not an option. Confirmed change in behavior from 23.11. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 23581] New: Do not fill hold when patron account has overdues/fines
by bugzilla-daemon＠bugs.koha-community.org 02 Oct '25

02 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23581 Bug ID: 23581 Summary: Do not fill hold when patron account has overdues/fines Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Would like to see a preference that would keep a patron from advancing and/or having holds filled in the queue if they have overdue items and/or fines. This could be used as an incentive to return items on time and not play the system in some ways, especially in libraries that don't charge fines. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 39166] New: 'Transfers to send' report only appears if StockRotation syspref is enabled but contains information about other types of transfers
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '25

01 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39166 Bug ID: 39166 Summary: 'Transfers to send' report only appears if StockRotation syspref is enabled but contains information about other types of transfers Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation 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.m.hall(a)gmail.com The link to the 'Transfers to send' report is determined by the StockRotation syspref. However, I was playing with various types of transfers and noticed that the report actually contains other types of transfers (but not all). Should we remove the if StockRotation condition? To recreate: 1. Manually transfer an item to another library 1.1. Go to Circulation > Transfer 1.2. Choose another library (e.g. Liberty) 1.3. Enter a barcode for an item from Centerville (e.g. 39999000000771) 1.4. Click 'Transfer' 2. Place a hold for a Centerville item to be sent to another library 2.1. Search for Shakespeare grammar 2.2. Click 'Place hold' 2.3. Search for a non-Centerville patron (e.g. Henry Acevedo) 2.4. In 'Pickup at' choose Midway 2.5. Click 'Place hold' 3. Create a rotating collection 3.1. Go to Tools > Rotating collections 3.2. Click 'New collection' 3.3. Enter a title (e.g. Local authors) 3.4. Click 'Submit' 3.5. Click 'Return to rotating collections home' 4. Add items to the rotating collection 4.1. Click 'Actions' > 'Manage items' 4.2. Enter a couple of barcodes for items from Centerville and click 'Submit' after each - 39999000002195 - 39999000006933 - 39999000000719 5. Transfer collection 5.1. Click 'Transfer' 5.2. Choose a library (e.g. Springfield) 5.3. Click 'Transfer collection' 6. Go to Circulation --> There is no 'Transfers to send' report even though I do have 5 transfers to send 7. Enable StockRotation system preference 7.1. Go to Administration > System preferences 7.2. Search for StockRotation 7.3. Enable StockRotation 7.4. Click 'Save all Circulation preferences' 8. Go to Circulation --> There is the 'Transfers to send' report 9. Click 'Transfers to send' --> Transfers for the rotating collections are present, but not the manual transfer or the hold -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 33448] New: staffaccess permission needs to have 'permissions' removed from description
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '25

01 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33448 Bug ID: 33448 Summary: staffaccess permission needs to have 'permissions' removed from description Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com staffaccess no longer controls whether a staff member can modify user permissions. That is now controlled by the permissions permission. The staffaccess description needs to be updated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 34132] New: Undo batch Item modification
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '25

01 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34132 Bug ID: 34132 Summary: Undo batch Item modification Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl >From background_jobs.pl there could be a button to undo or reverse a batch item modification -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 28500] New: Display before and after values when a biblio has been edited
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '25

01 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28500 Bug ID: 28500 Summary: Display before and after values when a biblio has been edited 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: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Trying to determine what information was changed in a biblio is rather difficult. While there is some functionality in the logs, not all staff have access to the logs, nor is the info easy to interpret. It would be really helpful to have another method of tracking changes to bib records, such as a simple BEFORE value: xxxx AFTER value: xxxxx that only records the changes made, which user made the change, and when. Ideally this would be viewable outside of logs, perhaps through reports, and kept for the entire time the biblio is in the catalog. This is very important for libraries that have multiple locations and multiple staff editing biblios - there is a need to see who made what changes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 37605] New: Why do the vue apps use 'dialog' in place of modals?
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '25

01 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37605 Bug ID: 37605 Summary: Why do the vue apps use 'dialog' in place of modals? Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 I find the vue apps all use dialog where I feel 90% of the time it would be much more appropriate to use a bootstrap modal. The inconsistency is stark. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[Bug 31256] New: Circ rules batch modification
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '25

01 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31256 Bug ID: 31256 Summary: Circ rules batch modification Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Wouldn't it be nice if you could batch modify rules? Like, I have to set a hard due date for schools each year. Instead of modify each rule individually, it would be great if I could specify all libraries, or specific ones, all rules under that or specific ones, and what I would change. There are times when we have to change the fines to everything, or change the holds to many rules, etc. This would make this job so much easier. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 31971] New: SIP server rejects passwords ending in non-alphanumeric characters
by bugzilla-daemon＠bugs.koha-community.org 01 Oct '25

01 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31971 Bug ID: 31971 Summary: SIP server rejects passwords ending in non-alphanumeric characters Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1 - Set a patron's password to secret* 2 - Attempt a patron information request via the sip clip emulator: perl misc/sip_cli_emulator.pl -su term1 -sp term1 -l CPL -a localhost -p 6001 -m patron_information --patron ballard --password secret* 3 - It fails? 4 - Set password to secret*s 5 - Repeat perl misc/sip_cli_emulator.pl -su term1 -sp term1 -l CPL -a localhost -p 6001 -m patron_information --patron ballard --password secret*s 6 - It succeeeds Offending line(s) appears to be: 366 $buffer =~ s/^\s*[^A-z0-9]+//s; 367 # Every line must start with a "real" character. Not whitespace, control chars, etc. 368 $buffer =~ s/[^A-z0-9]+$//s; 369 370 # Same for the end. Note this catches the problem some clients have sending empty fields at the end, like ||| -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2