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

[Bug 19501] New: New list category to restrict specific lists to staff & hide from OPAC
by bugzilla-daemon＠bugs.koha-community.org 13 Sep '26

13 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19501 Bug ID: 19501 Summary: New list category to restrict specific lists to staff & hide from OPAC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: Jeremy.evans(a)nibsc.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We are creating various lists of titles that need to be hidden from view in the OPAC for the time being but other staff members need to see them. At the moment the options are Public or Private so this won't do what we require. We would like an additional list category selection of Staff so that those lists are then visible in the staff client (& presumably also to anyone who logs into the OPAC with a staff permissions login) but are not publicly visible in the OPAC. The intention is that multiple staff members may need to add items to some of these lists. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53

[Bug 34632] New: Patron Importing should be a background job
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '26

12 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34632 Bug ID: 34632 Summary: Patron Importing should be a background job Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi friends, Now that we have a lovely queue for our background jobs, we should make the patron import use the queue to process those and store the outcome. This will help us avoid the 500/600/whatever you set apache timeouts experienced by libraries whenever they import batches of patrons of any significant size. Cheers, Liz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53

[Bug 21052] New: New patron card printer profile won't save if paper bin is empty
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '26

12 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21052 Bug ID: 21052 Summary: New patron card printer profile won't save if paper bin is empty Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When adding a new printer profile in the patron card creator tool, you can save without entering a paper bin, but it will not create a new entry in the database. There is no error, the field is not marked as required. To test: - Add a new printer profile - Fill in description, leave other fields unchanged - Save - Verify that the new printer profile doesn't appear in the list and hasn't been created -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 40117] New: Add option for modification of not for loan from items tab
by bugzilla-daemon＠bugs.koha-community.org 12 Sep '26

12 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40117 Bug ID: 40117 Summary: Add option for modification of not for loan from items tab Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Not for loan is a powerful status with a lot of flexibility for libraries, especially since it has the -/+ holdable but not circulating/does not circulate capability. And many libraries are not using it to full advantage because the only way to edit it is from the edit item form, not easily accessible from the items page (moredetail.pl) like other statuses. It would be nice if, perhaps by system preference, a library could optionally make editing of the not for loan status available from moredetail.pl. That way libraries that want NFL status updating a bit more locked down can still only access it from editing an item, and libraries that want staff to be able to use more flexible statuses make it more accessible to staff. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 38990] New: Statistical patron checkouts don't display alert that LOST value has been cleared
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38990 Bug ID: 38990 Summary: Statistical patron checkouts don't display alert that LOST value has been cleared 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: catrina(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 37505 resolved getting information about items when checking them out to statistical patrons, however lost values (aside from Claims) do not alert or display that it has been resolved when checked out to the statistical patron as of 24.05.06. To test: 1. Create a Statistical Patron 2. Set BlockReturnOfLostItems to Don't Block. 3. Mark an item as missing. 4. Check it out to the Statistical Patron. 5. You get a message "Local use recorded." <- You should see a message, "Item was lost, but has now been found." 6. Check your item - the lost value has been cleared and is now available. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 36868] New: Add ability to automatically empty cart after placing holds ( staff interface and OPAC )
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36868 Bug ID: 36868 Summary: Add ability to automatically empty cart after placing holds ( staff interface and OPAC ) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 Some librarians would like to have the cart automatically clear itself after placing holds on items in the current cart. This would behave similar to how online retail/e-commerce sites work after one has purchased items. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 111

[Bug 38187] New: Add ability to delete patron attributes in batch patron modification
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38187 Bug ID: 38187 Summary: Add ability to delete patron attributes in batch patron modification 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: enica(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com You can batch modify patron attribute in a batch, but you cannot completely delete the attribute on a patron's account. To test: - Add an attribute to a patron's account. - Perform batch patron modification. - Under Patron attribute you can either add a new attribute or update existing one. You can set the attribute to blank to clear the values, but the attribute will remain on the account as blank. It would be nice if there's a way to delete the patron attribute all together. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 20344] New: Transferring an item while on hold results in a transfer were the destination is the same as the source
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20344 Bug ID: 20344 Summary: Transferring an item while on hold results in a transfer were the destination is the same as the source 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: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com 1. Check out an item 2. Place a hold on the specific item with a pickup at a different branch 3. Check in: Confirm hold and transfert 4. Check the branchtransfers table to ensure that the transfert is here SELECT * FROM branchtransfers order by datesent DESC LIMIT 10; 5. Home › Circulation › Transfers 6. Create a transfer identical as the existing one 7. You should see «Item is already at destination library.» 8. Check the branchtransfers table 1. First one should have been canceled «Canceled, new transfer from A to A created» 2. Another one should have been created from A to A 3. These 2 things are the issue. Because doing the same without a hold - doesn't create a new transfer - doesn't cancel the first one -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 39314] New: RabbitMQ can't upgrade from 3.x to 4.x without running a data migration on 3.13
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39314 Bug ID: 39314 Summary: RabbitMQ can't upgrade from 3.x to 4.x without running a data migration on 3.13 Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Reported to Debian as it affects their next release which will do a jump from 3.10 to 4.0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100165#10 Which can't work: https://www.rabbitmq.com/docs/upgrade «You can only upgrade to RabbitMQ 4.0 from RabbitMQ 3.13.» «stable feature flags have to be enabled before the upgrade. The upgrade will fail if you miss this step.» See there more more details. ----- For us: is there still data in RabbitMQ when stopping a Koha instance and upgrading it? I recall reading that the DB was basically mirroring the message queue data during a discussion about the actual need for a dedicated message queue. Does it mean the koha-common package can wipe the RabbitMQ data which will allow it to start without issue? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 37645] New: Add ability to batch waive fines
by bugzilla-daemon＠bugs.koha-community.org 11 Sep '26

11 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37645 Bug ID: 37645 Summary: Add ability to batch waive fines Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: enica(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice if there's an ability in Koha to waive fines/fees in a batch. This is part of a regular workflow for libraries, especially those who regularly purge patron accounts. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 59