June 2021 - Koha-bugs - lists.koha-community.org

[Bug 27813] New: Purchase suggestions should sort by suggesteddate rather than title
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '22

09 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27813 Bug ID: 27813 Summary: Purchase suggestions should sort by suggesteddate rather than title Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Prior to 20.05, suggestions on /cgi-bin/koha/suggestion/suggestion.pl sorted by suggesteddate by default. On 20.05 and later, they're sorting by title instead. We should go back to the previous behavior. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 27442] New: Circulation Module Report "Overdues" does not accurately show overdues by date
by bugzilla-daemon＠bugs.koha-community.org 08 Jul '22

08 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27442 Bug ID: 27442 Summary: Circulation Module Report "Overdues" does not accurately show overdues by date Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I believe the SQL is wrong in the hardcoded report "Overdue" under the Circulation Module. When a due date range is added when running the report, it is not showing the items that are overdue for a particular date, a library will need to run a range of 2 days to find out the day's overdue. Steps to Recreate: 1. Run Overdue report 2. Use the filter on the left to enter the date due to range of 10/12- 10/12. 3. No results are found with the actual date due to 10/12 4 Run the same report using the filter set at 10/12 - 10/13. 5 Koha will provide items that are due on 10/12. The SQL is looking at date_due rather than date(date_due) which is not giving accurate results. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 27070] New: Elasticsearch - with Elasticsearch 6 searches failing unless all terms are in the same field
by bugzilla-daemon＠bugs.koha-community.org 08 Jul '22

08 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27070 Bug ID: 27070 Summary: Elasticsearch - with Elasticsearch 6 searches failing unless all terms are in the same field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com To recreate - be using Elasticsearch 6 in KOha On sample data try searching for: street shuffle cool, that works Now try searching for a word from title and the publisher name: shuffle constable No results, odd. Try searching for: shuffle AND constable That works. I cannot figure from the docs why this is the case - we pass a default operator, that should be enough I thought, but no. https://www.elastic.co/guide/en/elasticsearch/reference/6.8/query-dsl-query… for comparison: https://www.elastic.co/guide/en/elasticsearch/reference/5.6/query-dsl-query… After testing the type => 'cross_fields' seems to do what we want -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35

[Bug 28219] New: Additional fields for orders/order lines
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '22

07 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28219 Bug ID: 28219 Summary: Additional fields for orders/order lines Change sponsored?: --- Product: Koha Version: unspecified 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 It's possible to add additional fields to baskets and subscriptions, but it would be great if this could be extended to other areas as well. One of those would be orders (order lines) We currently have 2 statistical fields, but sometimes this is not enough. There are new demands on libraries with Open Access and APC management where it could be helpful to have some more flexibility here. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 15774] New: Additional fields for baskets
by bugzilla-daemon＠bugs.koha-community.org 07 Jul '22

07 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15774 Bug ID: 15774 Summary: Additional fields for baskets Change sponsored?: 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: jweaver(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: nicole(a)bywatersolutions.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 197

[Bug 25220] New: maxoutstanding syspref should be disabled by a null value
by bugzilla-daemon＠bugs.koha-community.org 06 Jul '22

06 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25220 Bug ID: 25220 Summary: maxoutstanding syspref should be disabled by a null value 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 Several fines-related system preferences (OPACFineNoRenewals, noissuescharge, etc) can be disabled by leaving them blank. But maxoutstanding treats a blank as a zero, blocking OPAC holds for *any* fine balance. I'd like this to change to match the functionality of the other sysprefs. If nothing else, we should add some language to say a blank is treated as a zero. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 24091] New: Add biblionumber and itemnumber in Item lost reports
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '22

05 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24091 Bug ID: 24091 Summary: Add biblionumber and itemnumber in Item lost reports Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 28152] New: Hidden error when importing an item with an existing itemnumber
by bugzilla-daemon＠bugs.koha-community.org 05 Jul '22

05 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28152 Bug ID: 28152 Summary: Hidden error when importing an item with an existing itemnumber Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Tools 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 are trying to insert "duplicate item barcode" into import_items.itemnumber (integer), it fails with "Incorrect integer value: 'duplicate item barcode' for column 'itemnumber' at row 1" To reproduce: Export a biblio with an item Import it => The item is not added, and there is no new row in import_items. -- You are receiving this mail because: You are watching all bug changes.

1 36

[Bug 27857] New: Koha::Patron->extended_attributes skips checks
by bugzilla-daemon＠bugs.koha-community.org 04 Jul '22

04 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27857 Bug ID: 27857 Summary: Koha::Patron->extended_attributes skips checks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Patron attributes can have some requirements: - Be unique across the DB - (Not) bd repeatable This is correctly handled by both - Koha::Patron::Attribute->store - Koha::Patron->add_extended_attribute But then, there's Koha::Patron->extended_attributes, that can overwrite them all at once, but doesn't rely on those methods, and uses DBIC relations instead, so no checks on attribute constraints are made. We need to fix it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 58

[Bug 28454] New: Add Koha version number to database schema link in reports
by bugzilla-daemon＠bugs.koha-community.org 03 Jul '22

03 Jul '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28454 Bug ID: 28454 Summary: Add Koha version number to database schema link in reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org In reports, the link to the database schema points to the main page and the user must select their version. We know what version they're using, so we should append the version number to the link so that it takes them directly there. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32