December 2024 - Koha-bugs - lists.koha-community.org

[Bug 27115] New: Restarting koha-common fails to restart SIP2 server
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27115 Bug ID: 27115 Summary: Restarting koha-common fails to restart SIP2 server Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com Sometimes when we run "systemctl restart koha-commmon" the SIP server doesn't get restarted but might just get stopped leading to longer than expected downtime. There is probably some sort of race condition. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 24364] New: Display item holding library in opac issues
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24364 Bug ID: 24364 Summary: Display item holding library in opac issues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Be able to display the item's holding library in OPAC issues. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 38291] New: Add GET /library_groups
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38291 Bug ID: 38291 Summary: Add GET /library_groups 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: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com We should have an endpoint to list library groups -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 35903] New: In cataloguing authority plugin using autocomplete must set operator exact
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35903 Bug ID: 35903 Summary: In cataloguing authority plugin using autocomplete must set operator exact Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When cataloguing and using authority plugin, there is auto-completion on inputs and default operator is "contains". When using auto-completion and selecting a result it would be logical to set operator "exact" and submit form. So the usually unique result appears. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 38192] New: DT - State not restored correctly on suggestion tables
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38192 Bug ID: 38192 Summary: DT - State not restored correctly on suggestion tables Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal 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: 33426 There is one table per tab, the id of the table is table_N. Say you have: Pending (#table_1), Accepted (#table_2), Rejected (#table_3) The state will be stored in localStorage with the following key: DataTables_table_1_/cgi-bin/koha/suggestion/suggestion.pl DataTables_table_2_/cgi-bin/koha/suggestion/suggestion.pl DataTables_table_3_/cgi-bin/koha/suggestion/suggestion.pl If you move all the suggestions from Accepted to Rejected, a shift will give: Pending (#table_1), Rejected (#table_2) And the previous state from the "Accepted" tab will be used for "Rejected" Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33426 [Bug 33426] Add client storage of user-selected DataTables configuration to suggestion.tt -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 37530] New: Enhance the confirm cashup modal in the Point of sale module
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '26

16 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37530 Bug ID: 37530 Summary: Enhance the confirm cashup modal in the Point of sale module Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Point of Sale Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com When doing a cashup on the registers.pl page in the POS module, it would be helpful to be able to have specific information about the previous time period's sales before actually recording the cashup. Currently, when you perform the cashup the only information you get is how much money you should be removing from the register and how much of a float to leave. Although the table on the cash summary page gives some information, the modal gives no information about how much money you should have in cash, credit cards or checks. No information about refunds. No information about the actual debit types that were sold. This is critical information for us because we handle sales for three entities - the library, Friends of the Library and Library Foundation. There is a 'cashup summary' link in the 'last cashup' column which gives a nice breakdown of this type of information but that's for the last cashup you performed not the one you are about to do. In fact, when we were learning POS we kept expecting this info to match the sales we were about to cashup. A report (based on the current 'cashup summary' report ) of the transactions since the last cashup, along with the current information you get when clicking on the 'Record cashup' button would be helpful. The information could be presented on screen and allow printing prior to actually confirming the cashup. Another reason an enhanced 'Record cashup' modal would be helpful is that we have had to create customized reports to get this detailed information. If it could be presented during the cashup process we could print the information for our own records and send it to our Finance Dept. with our daily deposit. I've added a screenshot to offer more clarification. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 35754] New: Place multiple item-group holds at once for the same record
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35754 Bug ID: 35754 Summary: Place multiple item-group holds at once for the same record 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: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With the availability for item-groups and item group holds it make it very easy for patrons to place a hold on a group of items. This enhancement would provide an option to place multiple item-group holds for the same record. An example use case could be a patron wants to place a hold on volume 4, 5, and 6. Current behavior requires the user to place a hold for vol 4, then place another for vol 5, then finally place a hold for vol 6. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 19060] New: Patrons should not get a max fines block auto-renewal notification for items due in the future.
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19060 Bug ID: 19060 Summary: Patrons should not get a max fines block auto-renewal notification for items due in the future. Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: r.delahunty(a)arts.ac.uk QA Contact: testopia(a)bugs.koha-community.org This appears related to 19014. Current functionality in 17.05: Auto-renewal is enabled for specific user and item type combinations. This user has fines in excess of that specified in OPACFineNoRenewalBlockAutoRenewal This user has an item due today, and others due at various times in the future, some many weeks ahead. When the auto-renewal job runs today, Koha is sending an AUTO_RENEWAL email to this user for each of the items on loan, warning that each has failed automatic renewal. Desired functionality in 17.05: When the auto-renewal job runs, Koha should only send an AUTO_RENEWAL failure email to the user for item(s) due for automatic renewal today. Other items are still validly on loan and are not due for renewal. The user is being contacted multiple times unnecessarily and this can be confusing. Ray Delahunty University of the Arts London -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 37097] New: koha is not responding due to lack of free disk space (zebra tmp suddenly grows)
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37097 Bug ID: 37097 Summary: koha is not responding due to lack of free disk space (zebra tmp suddenly grows) Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: yuriy.kotsyuk(a)oa.edu.ua Periodically we have a problem with free space on our koha server on Ubuntu 20.04.6. The total disk capacity is 210 GB (koha usually takes 105 GB), but sometimes the number of files in /var/lib/koha/library/biblios/tmp suddenly grows and takes up all the free disk space. As a result, koha server starts working with errors and stops completely. I have come to the conclusion that this folder holds temporary zebra files. I just clear the tmp folder each time. After that, the koha wakes up. Is that an issue with a small disk, or is that an issue with periodical cleaning tmp folder? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 36724] New: Add cartographic mathematical data to Elasticsearch index mappings
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '26

13 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36724 Bug ID: 36724 Summary: Add cartographic mathematical data to Elasticsearch index mappings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz Search whole 255 field https://www.loc.gov/marc/bibliographic/bd255.html Test with values like * Scale 1:22,000,000 * Conic proj. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22