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

[Bug 14787] Allow confirm/continue option to circulation warnings at checkout
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14787 Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to main |Needs documenting --- Comment #20 from Lucas Gass (lukeg) <lucas(a)bywatersolutions.com> --- Enhancement won't be backported to 24.05.x -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 32772] New: Patron autocomplete should not use contains on all fields
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32772 Bug ID: 32772 Summary: Patron autocomplete should not use contains on all fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 31782 added all default patron search fields to the autocomplete, and made them all use 'contains' This makes searching in large systems difficult Previous behaviour: Every library has a unique starting cardnumber sequence, but it can repeat in later numbers Library A types "3A" to find their patrons only, but autocomplete now returns all of library B patrons with cards ending in 3A Other issue: Library has a large number of patrons with surnames 'Williams' and 'Fitzwilliams' Type 'Williams' into the search, only see Fitzwilliams I think we should default to 'Starts with' which allows the use of '%' at the start to make it a contains, rather than force contains which we don't have a way to limit. Otherwise, we need to support '^' for starts with -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 36635] New: Cannot display vendor's issue
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36635 Bug ID: 36635 Summary: Cannot display vendor's issue Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Acquisitions Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 36192 acqui/vendor_issues.pl:if ( $op eq 'add_form' || $op eq 'cud-show' ) { Should be "show" not "cud-show" Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36192 [Bug 36192] [OMNIBUS] CSRF Protection for Koha -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 38638] New: Offer the option to set non-priority option when placing multiple holds
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38638 Bug ID: 38638 Summary: Offer the option to set non-priority option when placing multiple holds Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 22789 When placing multiple holds in the staff interface there isn't an option to set the holds as non-priority. As far as I know there's not a technical reason not to include the option? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22789 [Bug 22789] Establish non-priority holds -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 22789] New: Establish Non-Priority Holds
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22789 Bug ID: 22789 Summary: Establish Non-Priority Holds 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: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- This development would allow holds to be placed so the hold wouldn't prevent the current checkout from renewing the hold. The goal is a better customer service because certain library departments will place holds to repair or replace a book when it is returned to the library (the internal library need has no rush), they only want the catch the book on it's return. The library needs to allow the patron who has it out have the flexibility to renew it on their account without a staff override. This functionality would be specific to the staffside only. - Add a Checkbox on the hold form that stipulates that the hold being placed is a 'non-priority' hold. - Add a field in the reserves tables to flag the hold as 'non-priority'. - The checkreserves module in Koha checks for this flag. If found, the hold request is 'ignored' and item can be renewed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 35432] New: Clarify and simplify the workings of MapItemsToHoldRequests
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35432 Bug ID: 35432 Summary: Clarify and simplify the workings of MapItemsToHoldRequests 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This is a large and sparsely documented routine that could use some cleanup/explanation -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 37903] New: Timezone ignored when passing rfc3339 formatted date (POST, PUT, PATCH)
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37903 Bug ID: 37903 Summary: Timezone ignored when passing rfc3339 formatted date (POST,PUT,PATCH) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com When requesting the REST API we are getting datetimes in the RFC3339 format, for instance: 2024-09-04T06:03:34-03:00 This is retrieving the value that is stored DB, and using the timezone defined in the $KOHA_CONF file. However this format is not correctly into account when we search or, more importantly, when we create/update objects. Examples (Using the Buenos Aires timezome, which is UTC-3 "America/Argentina/Buenos_Aires"): 1. POST /api/v1/patrons with "due_date": "2024-09-09T23:59:00-00:00", And you will get "due_date": "2024-09-09T23:59:00-03:00", in DB: date_due: 2024-09-09 23:59:00 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 37952] New: Store datetime DB columns in UTC
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37952 Bug ID: 37952 Summary: Store datetime DB columns in UTC Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We need to store the datetime in UTC in DB and apply the timezone on display only. It will be more flexible and easier to maintain. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 38216] New: Objects.t failing on D10 and U20
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38216 Bug ID: 38216 Summary: Objects.t failing on D10 and U20 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org t/db_dependent/Koha/REST/Plugin/Objects.t .. 18/18 # Failed test 'No tests run for subtest "date handling"' # at t/db_dependent/Koha/REST/Plugin/Objects.t line 1041. Can't locate object method "rfc3339" via package "DateTime" at t/db_dependent/Koha/REST/Plugin/Objects.t line 1024. # Looks like your test exited with 255 just after 18. t/db_dependent/Koha/REST/Plugin/Objects.t .. Dubious, test returned 255 (wstat 65280, 0xff00) -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 37902] New: Timezone ignored when passing rfc3339 formatted date (search 'q')
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '24

05 Dec '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37902 Bug ID: 37902 Summary: Timezone ignored when passing rfc3339 formatted date (search 'q') Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com 2. GET /api/v1/jobs?q={"enqueued_on":{">":"2024-09-04T09:26:52-03:00"}} is generating the following query SELECT `me`.`id`, `me`.`status`, `me`.`progress`, `me`.`size`, `me`.`borrowernumber`, `me`.`type`, `me`.`queue`, `me`.`data`, `me`.`context`, `me`.`enqueued_on`, `me`.`started_on`, `me`.`ended_on` FROM `background_jobs` `me` WHERE `enqueued_on` > '2024-09-04T09:26:52-03:00' But when you run it manually, you get a warning: | Warning | 1292 | Truncated incorrect datetime value: '2024-09-04T09:26:52-03:00' | -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 58