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

[Bug 15261] Verify if checkout or hold request periods overlap with existing holds
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15261 --- Comment #124 from Arthur Suzuki <arthur.suzuki(a)biblibre.com> --- Created attachment 189915 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189915&action=e… Bug 15261: Add overlap reserve check in ILS-DI HoldTitle and HoldItem Test plan : - apply the tests patch. - prove t/db_dependent/ILSDI_Services.t => it should fail - apply fix patch and run the tests again. - tests should pass. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15261] Verify if checkout or hold request periods overlap with existing holds
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15261 --- Comment #123 from Arthur Suzuki <arthur.suzuki(a)biblibre.com> --- Created attachment 189914 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189914&action=e… Bug 15261: Add tests for overlapping reserves on ILS-DI -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15261] Verify if checkout or hold request periods overlap with existing holds
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15261 --- Comment #122 from Arthur Suzuki <arthur.suzuki(a)biblibre.com> --- Created attachment 189913 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189913&action=e… Bug 15261: Add tests for PreventChechoutOnSameReservePeriod and PreventReservesOnSamePeriod Created 2 new tests files Circulation/CanBookBeIssued.t and Reserves/ReserveDates.t Signed-off-by: Laurence Rault <laurence.rault(a)biblibre.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 15261] Verify if checkout or hold request periods overlap with existing holds
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15261 Arthur Suzuki <arthur.suzuki(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #187999|0 |1 is obsolete| | Attachment #188000|0 |1 is obsolete| | --- Comment #121 from Arthur Suzuki <arthur.suzuki(a)biblibre.com> --- Created attachment 189912 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=189912&action=e… Bug 15261: Check if checkout/reserve request overlaps existing reserves When checking out or placing hold, we should check if an existing reserve whose period overlap exists. - A user places a hold from opac whose requested period overlaps with an existing reserve period => prevent reserve - A librarian places a hold from staff whose requested period overlaps with an existing reserve period => Warn librarian (Ask for confirmation) - A librarian makes a checkout from staff whose requested period overlaps with an existing reserve period => Warn librarian (Ask for confirmation) Test plan: Enable syspref: AllowHoldDateInFuture OPACAllowHoldDateInFuture PreventChechoutOnSameReservePeriod and PreventReservesOnSamePeriod 1 (staff side): - Place a hold on title (which has only one items) level with start date and expiration date. - Place another hold (also title level) with period overlaping this reserve. - Check you are warned about an existing reserve 2 (staff side): - Place a hold on title (which has more than one items) level with start date and expiration date. - Place another hold (also title level) with period overlaping this reserve. - Check you are NOT warned about an existing reserve. Because it remains at least one item not reserved. 3 (staff side): - Place a hold on item level with start date and expiration date. - Place another hold on item level with period overlaping this reserve. - Check you are warned about an existing reserve. 4 (opac side): - Do the same than for staff side. Instead of a warn, reserve is prevented. 5: - Place a hold on title (which has only one items) level with start date and expiration date. - Try to checkout the unique item from this title with period overlaping the reserve period. - Check you are warned about an existing reserve 6: - Place a hold on title (which has more than one items) level with start date and expiration date. - Checkout an item from this title with period overlaping the reserve period. - Check you are NOT warned about an existing reserve. 7: - Place a hold on item level with start date and expiration date. - Checkout this item period overlaping the reserve period. - Check you are warned about an existing reserve 8: - Create a checkout (i.e from ${TODAY} to ${TODAY + 10 days}), - Place a hold on the same item from ${TODAY + 11 days} to ${TODAY + 30 days}), - Check that you cannot renew the checkout. Signed-off-by: Laurence Rault <laurence.rault(a)biblibre.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 41290] New: TooMany checkouts: Scope issues with onsite circulation rule
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41290 Bug ID: 41290 Summary: TooMany checkouts: Scope issues with onsite circulation rule Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com See 41280 (and 27834). The first rule block assumes that an onsite checkout has a regular rule. The same scope is applied as the regular rule. Could be wrong? The second rule block with patron max qty has a similar problem. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 37968] New: Add ability to store branchcode for messages in the queue and send by branchcode
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37968 Bug ID: 37968 Summary: Add ability to store branchcode for messages in the queue and send by branchcode Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We should be able to specify in the message queue who "owns" a message, and filter based on that data. We should limit it to the patron's branchcode for now, with the option to add sysprefs to control who "owns" each notice on a per-notice basis as a later enhancement as each notice has different things associated with it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 12488] Make bulkmarcimport.pl -d use DELETE instead of TRUNCATE
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12488 Jan Kissig <bibliothek(a)th-wildau.de> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=41008 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 41289] New: Email receipt not sent if payment is made via API
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '25

24 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41289 Bug ID: 41289 Summary: Email receipt not sent if payment is made via API Initiative type: --- Sponsorship --- status: 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: anni.maki-mantila(a)turku.fi QA Contact: testopia(a)bugs.koha-community.org If syspref AutomaticEmailReceipts is on, email receipt is getting sent only if the payment is made in staff interface. The receipt should get sent also if the payment is made via API. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 37398] New: Date Field changes from mm/dd/yyyy to 0000-00-00
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '25

23 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37398 Bug ID: 37398 Summary: Date Field changes from mm/dd/yyyy to 0000-00-00 Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: eric(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl A typed in value that follows the dateFormat system preference (mm/dd/yyyy) is changed to 0000-00-00 when the item is saved. This was found in 952$w before enabling the dateaccessioned.pl plugin for the subfield. To recreate: -set system preference dateFormat to mm/dd/yyyy -Go to an existing bib record -Edit items -input a date following the specified format (07-17-2024) -save the item -check the item and notice the date has been changed to 0000-00-00 -click back to the bib record -Error 500: Internal server error - Month out of range -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 95

[Bug 5323] koha package should install a setup that works with koha-common
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '25

23 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5323 --- Comment #4 from Robin Sheat <robin(a)kallisti.net.nz> --- Y'know what I'd consider? Have the koha package ask a bunch of questions using debconf and run "koha-create" based on that. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. You are watching all bug changes.

1 0