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

[Bug 19379] New: Selenium test for the list workflow
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '22

19 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19379 Bug ID: 19379 Summary: Selenium test for the list workflow Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: alexbuckley(a)catalyst.net.nz Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org The Selenium test patch for this bug report will add a biblio and items to that biblio. A list will be created and then the item will be added to the list. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 27195] New: Set focus for cursor to city input box when creating new cities
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '22

16 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27195 Bug ID: 27195 Summary: Set focus for cursor to city input box when creating new cities Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When adding a new city on cities.pl you have to click in the city input box, which is a required field, so that you can enter text. It would be more efficient to set the focus for the cursor to always be in the city input box so that you could just begin typing and eliminate an extra click. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 30923] New: OAuth2 implementation is not experimental
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '22

16 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30923 Bug ID: 30923 Summary: OAuth2 implementation is not experimental 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 CC: tomascohen(a)gmail.com We added a confusing warning on the sysprefs. OAuth2 has been used by third parties to interact with Koha in a secure way since its introduction back in 2018. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 18392] New: Allow importing/ exporting circulation conditions as CSV or spreadsheet
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '22

16 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18392 Bug ID: 18392 Summary: Allow importing/exporting circulation conditions as CSV or spreadsheet Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com As our circulation GUI is not perfect (yet) it would be nice if it offered a similar feature to the bibliographic frameworks, allowing to export/import the rules using CSV or spreadsheet files. This would make it much easier to update rules in bulk and keep track of changes to them as you could archive different versions easily too. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 31191] New: Specify FacetLabelTruncationLength is only for Zebra
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '22

16 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31191 Bug ID: 31191 Summary: Specify FacetLabelTruncationLength is only for Zebra Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When using ElasticSearch, the FacetLabelTruncationLength system preference doesn't apply. I don't know if it's a bug or by design. Maybe it should be indicated in the syspref description that it only works with Zebra? To test: 1) Change the searchengine syspref to Zebra 2) Reindex 3) Do a search 4) Check the facets --> The longer ones should be truncated to 20 characters 5) Change the seachengin syspref to Elasticsearch 6) Redo steps 2-4 --> The longer facets are displayed in full -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 31156] New: Document borrowers-force-messaging-defaults.pl in cronjobs chapter
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '22

16 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31156 Bug ID: 31156 Summary: Document borrowers-force-messaging-defaults.pl in cronjobs chapter Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I don't know if it can be considered a cronjob, it's mostly a command-line utility used once, afaik, but I've had to use it as a cronjob for a client who regularly imports borrowers. It is not in the manual at all, and I had trouble finding information on all the options. =head1 SYNOPSIS borrowers-force-messaging-defaults.pl borrowers-force-messaging-defaults.pl --help borrowers-force-messaging-defaults.pl --doit borrowers-force-messaging-defaults.pl --doit --not-expired borrowers-force-messaging-defaults.pl --doit --category PT =head1 DESCRIPTION If the EnhancedMessagingPreferences syspref is enabled after borrowers have been created in the DB, those borrowers won't have messaging transport preferences default values as defined for their borrower category. So you would have to modify each borrower one by one if you would like to send them 'Hold Filled' notice for example. This script creates/overwrites messaging preferences for all borrowers and sets them to default values defined for the category they belong to (unless you use the options -not-expired or -no-overwrite to update a subset). =over 8 =item B<--help> Prints this help =item B<--doit> Actually update the borrowers. =item B<--not-expired> Will only update active borrowers (borrowers who didn't pass their expiration date). =item B<--no-overwrite> Will only update patrons without messaging preferences and skip patrons that already set their preferences. =item B<--category> Will only update patrons in the category specified. See also Bug 31155 for --since option -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 29336] New: Some authorised_value FK fields are too short
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '22

15 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29336 Bug ID: 29336 Summary: Some authorised_value FK fields are too short 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org To mention a few: authorised_value | varchar(10) in authority framework additional fields `authorised_value_category` varchar(16) auth_tag_structure `authorised_value` varchar(10) COLLATE utf8mb4_unicode_ci DEFAULT NULL, borrower_attribute_types `authorised_value_category` varchar(32) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 21466] New: Data inconsistencies - items.location values must have a corresponding authorised value
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '22

15 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21466 Bug ID: 21466 Summary: Data inconsistencies - items.location values must have a corresponding authorised value Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz See bug 18355. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 29105] New: items responses do not respect effective_itemtype
by bugzilla-daemon＠bugs.koha-community.org 15 Sep '22

15 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29105 Bug ID: 29105 Summary: items responses do not respect effective_itemtype 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: martin.renvoize(a)ptfs-europe.com The item objects we return from various items API routes do not respect the effective itype offerings. Example, itype is mapped directly from the item itype field to item_type.. it should check for effective itemtype and return the result of that. Similarly notforloan is mapped directly, but can depend on the effective itemtype. There are possibly others. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 30641] New: Authority detail page shows wrong number of records using the authority
by bugzilla-daemon＠bugs.koha-community.org 14 Sep '22

14 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30641 Bug ID: 30641 Summary: Authority detail page shows wrong number of records using the authority Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal 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 You can see the wrong behaviour in a clean sample database with http://localhost:8081/cgi-bin/koha/authorities/detail.pl?authid=133 To test: * Test plan assumes you are using the ktd sample data * Staff interface > authorities * Search for agile * Verfiy the result list shows used by 2 records and this is correct (authority is linked to both of them) * Switch to authority detail page * Verify it shows 3 records use this authority * Verify this is incorrect (the second record is not linked to the authority) I suspect that the detail page doesn't do an exact/phrase search opposed to the other pages, finding also records with similar authority numbers? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18