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

[Bug 28470] New: Typo: Are you sure you with to chart this report?
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28470 Bug ID: 28470 Summary: Typo: Are you sure you with to chart this report? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Typo: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:1392 Fetching full chart data for reports with many rows can cause performance issues. Are you sure you with to chart this report? -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 28910] New: Correct eslint errors in OPAC basket.js
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28910 Bug ID: 28910 Summary: Correct eslint errors in OPAC basket.js Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Blocks: 23833 Following coding guideline JS8: "Follow guidelines set by ESLint," some errors should be corrected in the OPAC's copy of basket.js Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23833 [Bug 23833] [Omnibus] JavaScript should conform to coding guidelines recommended by ESLint -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 28913] New: Automatic checkin setting in item type setup should note required cronjob
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28913 Bug ID: 28913 Summary: Automatic checkin setting in item type setup should note required cronjob Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: andrew(a)bywatersolutions.com Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: bwsdonna(a)gmail.com, gmcharlt(a)gmail.com, kelly(a)bywatersolutions.com, sbrown(a)bywatersolutions.com Depends on: 23207 The automatic checkin feature introduced in bug 23207 requires a cron job. We should note that in item type setup so users don't expect the feature to start working simply because they checked the box. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23207 [Bug 23207] Allow automatic checkin/return at end of circulation period -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 28573] New: Replace authority record with Z39.50/SRU creates new authority record
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28573 Bug ID: 28573 Summary: Replace authority record with Z39.50/SRU creates new authority record Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: sebastian.krieg(a)tuz-eisenach.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When replacing an authority record with Z39.50/SRU you get a new record and no update of the upgrading record. Test instance: Catalyst IT Ltd. (New Zealand) (https://koha-community.org/demo/) example record: #13 (name: Plato) Steps to reproduce: 1. Menu "Home > Authorities > Details for authority #13 (Personal Name)" 2. Form: https://demo-intra.mykoha.co.nz/cgi-bin/koha/authorities/detail.pl?authid=13 3. Menu "Edit > Replace record via Z39.50/SRU" 4. Field "Name(any)": Homer >> Click "search" 5. choose the second entry "Aschmann, Homer, 1920-" >> click "import" Expected solution: - replace the record #13 with the search data "Aschmann, Homer, 1920-" - Form: https://demo-intra.mykoha.co.nz/cgi-bin/koha/authorities/detail.pl?authid=13 Error: - Menu "Home > Authorities > Adding authority Personal Name" - form: https://demo-intra.mykoha.co.nz/cgi-bin/koha/authorities/authorities.pl?bre… - Save the record as Record #14 - Menu "Home > Authorities > Details for authority #14 (Personal Name)" Note: I found this error in release 21.05., I use a instance 20.11. to reproduce the error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 28189] New: Move the base swagger file to YAML
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28189 Bug ID: 28189 Summary: Move the base swagger file to YAML Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com In order to be able to add better documentation on the API, we should move the base file to YAML, so we can add multi-line Markdown in it. It renders correctly with tools like Redoc. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 28613] New: Several objects.search-based routes missing parameters
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28613 Bug ID: 28613 Summary: Several objects.search-based routes missing parameters Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com The objects.search helper provides convenient ways to paginate and a 'q' filter parameter to build complex queries on this Koha::Objects-based routes. Some routes were created prior to this feature getting introduced. We need to adjust the parameters for all existing objects.search-based routes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 28585] New: Bug in GET /patrons by date_of_birth
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28585 Bug ID: 28585 Summary: Bug in GET /patrons by date_of_birth Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: hannamari.h.heiniluoma(a)jyu.fi Querying patrons by their date_of_birth returns an empty response, even though there are patrons with that date of birth in the database. Might be a bug? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 56

[Bug 27787] New: Point of Sale Receipt extra line
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '21

10 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27787 Bug ID: 27787 Summary: Point of Sale Receipt extra line 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 117283 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=117283&action=e… Double entry on receipt When printing a Point of Sale receipt (RECEIPT) under Notices and Slips, there is an extra line under the Description of Charges. There appears to be two lines dedicated to the charge- one with the description and one just blank, but showing the dollar ammount. Can we have the Koha notice, RECEIPT, changed to have only one line for the Description and charge, this is confusing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 16467] New: Discharge requests pending count should appear on patrons home page
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '21

10 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16467 Bug ID: 16467 Summary: Discharge requests pending count should appear on patrons home page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently the "Discharge requests pending" count appears only on the staff client home page. Like the count of patrons requesting modification, the discharge request count should also appear on the patrons home page (members-home.pl). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 24382] New: Wrong information showing on detail pages for fines/fees and payments
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '21

10 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24382 Bug ID: 24382 Summary: Wrong information showing on detail pages for fines/fees and payments Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees 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 _first_ table in a payment details page reads: Details of payment Date Description of charges Barcode Due date Return date Note Amount Outstanding This makes no sense - these are the columns for a fine or fee, but they don't apply well to a payment. When you compare to the table shown for a fine/fee, I think the table should actually display with these lines: Date created Date updated Amount Amount outstanding Type Note Transacting librarian Date/time of change Amount of change Type of change -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3