September 2022 - Koha-bugs - lists.koha-community.org

[Bug 26639] New: Turn auto_savepoint ON
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26639 Bug ID: 26639 Summary: Turn auto_savepoint ON Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org We have been adding transactions a lot lately, and we have just found that we are expecting a behaviour that is not the one we have. Take a look at the code posted on bug 26518 comment 7. If we turn auto_savepoint on, we will get the behaviour we expect. This patch has been initially attach on bug 21684 comment 2, but then dropped. See also https://metacpan.org/pod/distribution/DBIx-Class/lib/DBIx/Class/Manual/Cook… -- You are receiving this mail because: You are watching all bug changes.

1 32

[Bug 26529] New: Holds rules enforced incorrectly when not set at library level
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26529 Bug ID: 26529 Summary: Holds rules enforced incorrectly when not set at library level Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1 - Set ReservesControl to item home library 2 - confirm your circ rules allow holds at both the All Libraries and library-specific levels 3 - confirm Default checkout, hold and return policy is totally unset at both the All Libraries and library-specific levels 4 - place a hold on an item at Branch A for pickup at Branch A 5 - check item in, confirm hold triggers 6 - cancel hold 7 - go to Default checkout, hold and return policy for Branch A 8 - enter 1 for Total current checkouts allowed, save that with no other values entered 9 - re-place hold, confirm no error when placing hold 10 - check item in, hold does not trigger 11 - set Hold policy and Hold pickup library match at to Any Library at All Libraries level 12 - confirm hold still doesn't capture set Hold policy and Hold pickup library match at to Any Library for Branch A 13 - confirm hold now captures If these rules aren't set at the branch level we should be falling back to All Libraries. If they're not set anywhere, we should be assuming holds are allowed is the circ rules allow them. Starting from default testing docker data, this is what my db shows at step 7: MySQL [koha_kohadev]> select * from circulation_rules; +----+------------+--------------+----------+-------------------+------------+ | id | branchcode | categorycode | itemtype | rule_name | rule_value | +----+------------+--------------+----------+-------------------+------------+ | 1 | NULL | NULL | NULL | maxissueqty | 5 | | 2 | NULL | NULL | NULL | maxonsiteissueqty | 5 | +----+------------+--------------+----------+-------------------+------------+ And this is what it shows at step 8: MySQL [koha_kohadev]> select * from circulation_rules; +----+------------+--------------+----------+--------------------------+------------+ | id | branchcode | categorycode | itemtype | rule_name | rule_value | +----+------------+--------------+----------+--------------------------+------------+ | 1 | NULL | NULL | NULL | maxissueqty | 5 | | 2 | NULL | NULL | NULL | maxonsiteissueqty | 5 | | 8 | CPL | NULL | NULL | patron_maxissueqty | 1 | | 9 | CPL | NULL | NULL | returnbranch | | | 10 | CPL | NULL | NULL | hold_fulfillment_policy | | | 11 | CPL | NULL | NULL | patron_maxonsiteissueqty | | | 12 | CPL | NULL | NULL | max_holds | | +----+------------+--------------+----------+--------------------------+------------+ I cannot recreate this on master. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 20755] New: Allow separate email configuration for acq emails
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20755 Bug ID: 20755 Summary: Allow separate email configuration for acq emails Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment the emails in acuisistion (claims and orders) are sent with the email address of the librarian that triggers the sending. This is not practical in all cases for several reasons and it would be nicer if a general acquisition team email could be used. The development should allow to configure the email on library level with a from, replyto and returnpath address similar to the branchemail and it's options. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 31575] New: Missing warning for holds where AllowHoldPolicyOverride can be used to force a hold to be placed
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31575 Bug ID: 31575 Summary: Missing warning for holds where AllowHoldPolicyOverride can be used to force a hold to be placed 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If some holds are overridable, and AllowHoldPolicyOverride is enabled, Koha used to "flag" each holdable item to let librarians know the hold could not normally be placed. In 22.05 up to current master as of this writing, no warning is displayed. Test Plan: 1) Set one circ rule to allow 0 holds 2) For Library A, set "Hold pickup library match" to "item's hold group" 3) Enable AllowHoldPolicyOverride 4) Set ReservesControlBranch to "item's home branch" 5) Create a record with an item for Library A, one for Library B, and one for Library C This should create a scenario where A's item cannot be held, and B and C's items must be overridden 6) Note you get the "Cannot place hold" but can place those holds anyway without a "warning" sign -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 31477] New: Switch icon for inventory
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '23

30 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31477 Bug ID: 31477 Summary: Switch icon for inventory 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 31162 The 'chart' icon doesn's quite capture inventory for me. I think list-check or ballot-check would capture the tool's purpose better. You are working through your items and check what's there or missing... https://fontawesome.com/icons/clipboard-check?s=solid Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31162 [Bug 31162] Add a clear cataloguing module home page -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 17499] New: Koha objects for messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 30 Nov '23

30 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17499 Bug ID: 17499 Summary: Koha objects for messaging preferences Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Create Koha objects for messaging preferences. We need to create REST API endpoint for managing patron messaging preferences and this is the first step. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 241

[Bug 21384] New: ILL requests table - allow patron sorting by last name
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21384 Bug ID: 21384 Summary: ILL requests table - allow patron sorting by last name Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Currently only sorting by first name is possible. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 30379] New: Create granular permissions for ILL
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30379 Bug ID: 30379 Summary: Create granular permissions for ILL Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: Niamh.WalkerHeadon(a)hse.ie Currently, there is only one permission for ILL on the system. Make these more granular. For example. Allow a staff member to create a request for a patron but don't allow them to manage the request in anyway. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 30208] New: Marking an item lost should revert the waiting status of any associated hold
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30208 Bug ID: 30208 Summary: Marking an item lost should revert the waiting status of any associated hold 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If an item is currently Waiting for pickup for a hold, editing that item to apply a lost status should revert the waiting status of the hold. To recreate: - place an item-level hold - check your item in and confirm the hold - confirm on waitingreserves.pl that Koha shows the item is waiting for pickup - confirm on the request.pl that Koha shows the item is waiting for pickup - edit your item to Lost - confirm the item now shows as both lost and waiting -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 21236] New: Restore ability to selectively set item to lost without generating fee
by bugzilla-daemon＠bugs.koha-community.org 29 Nov '23

29 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21236 Bug ID: 21236 Summary: Restore ability to selectively set item to lost without generating fee Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Prior to bug 19974 a user could set an item to lost via additem.pl and the item would not be marked as returned and the patron would not be charged the replacement cost. The previous bug sought to standardize behavior between additem.pl and moredetail.pl, making both pages mark lost items and returned and charge the patron. Based on feedback about existing library workflows that relied upon the discrepancy between to two behaviors, the MarkLostItemsasReturned syspref was added to give libraries a choice of when and if an item would be marked as returned when set to lost. However, no such syspref was added to give the option to maintain the inconsistent legacy behavior in charging replacement costs when items are lost. This breaks existing workflows for libraries using lost status to handle Claims Returned items where the intent is to mark an item as lost but not charge the patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4