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

[Bug 29352] New: Runtime parameter labels should not be said to be optional
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29352 Bug ID: 29352 Summary: Runtime parameter labels should not be said to be optional Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Reports Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 27644 If you use the "Insert runtime parameter" button when editing an SQL report the modal window for defining a label says that the label is optional and will allow no label to be selected. This is wrong. If there is no label the parameter will be treated as a generic text input. The interface should enforce the field as required. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27644 [Bug 27644] Add button to SQL report editor for inserting runtime parameters -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 29328] New: Add "list" to parameter dropdown
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29328 Bug ID: 29328 Summary: Add "list" to parameter dropdown 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 27380, 27644 The new List parameter isn't included in the new Insert Parameter dropdown. It should be. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27380 [Bug 27380] Add option for taking a list parameter in reports https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27644 [Bug 27644] Add button to SQL report editor for inserting runtime parameters -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

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 29152] New: Change to default search behavior when limiting by branch
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29152 Bug ID: 29152 Summary: Change to default search behavior when limiting by branch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 21249 Prior to bug 21249, branch limits in searching were enforced based on the item homebranch. Bug 21249 introduces a syspref to control how those limits are enforced. That's good. But on update the syspref is set to limit based on BOTH homebranch and holdingbranch. That's bad. >From 21249: $dbh->do(q{INSERT IGNORE INTO systempreferences (variable, value, options, explanation, type) VALUES ('SearchLimitLibrary', 'both', 'homebranch|holdingbranch|both', "When limiting search results with a library or library group, use the item's home library, or holding library, or both.", 'Choice')}); Should we not make that default to homebranch in order to not silently change how searches work? This makes a *huge* difference in search results. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21249 [Bug 21249] Syspref to choose whether to search homebranch, holding branch or both for library groups in advanced search -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 14999] Adding to basket orders from staged files mixes up the prices between different orders
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14999 Fridolin Somers <fridolin.somers(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to stable |Pushed to oldstable Version(s)|21.11.00,21.05.05 |21.11.00,21.05.05,20.11.12 released in| | CC| |fridolin.somers(a)biblibre.co | |m --- Comment #17 from Fridolin Somers <fridolin.somers(a)biblibre.com> --- Pushed to 20.11.x for 20.11.12 -- You are receiving this mail because: You are watching all bug changes.

1 0

[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 11350] Holds offered to patrons who are not allowed to put the item on hold
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11350 Sara Brown <sbrown(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrown(a)bywatersolutions.com Version|unspecified |21.05 --- Comment #4 from Sara Brown <sbrown(a)bywatersolutions.com> --- I'm seeing this on 21.05.04. Settings: -ReservesControlBranch set to 'item's home library' -Patron X created in category LIMITED with home library EAST -Circ rules at library EAST allow category LIMITED patrons to place holds on item type ADULTBOOK -Circ rules at library WEST prevent category LIMITED patrons from placing holds on item type BOOK -Bib 999 has items with itype ADULTBOOK (all home library EAST) and BOOK (all home library WEST) Steps: -Make ADULTBOOK copy of bib 999 unavailable via checkout to unrelated patron (etc.) -Place bib-level hold on bib 999 for patron X - WEST-owned BOOK copy shows correctly as unavailable for item-level hold in 'Place a hold on a specific item' section Then both: -The WEST-owned BOOK copy of bib 999 appears on WEST's next holds queue run for patron X, and also -Checking in the BOOK copy of bib 999 triggers the hold for patron X -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[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