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

[Bug 33423] New: Cypress - Using UI to login is against best practice
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '24

12 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33423 Bug ID: 33423 Summary: Cypress - Using UI to login is against best practice Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Depends on: 32030 https://docs.cypress.io/guides/references/best-practices#Organizing-Tests-L… We should update the way we login in for our cypress tests using the logging in recipes in the above link (if possible?), and not login through UI, as we are at the moment. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32030 [Bug 32030] Electronic resource management (ERM) -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 30362] New: GetSoonestRenewDate is technically wrong when NoRenewalBeforePrecision set to date soonest renewal is today
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '24

12 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30362 Bug ID: 30362 Summary: GetSoonestRenewDate is technically wrong when NoRenewalBeforePrecision set to date soonest renewal is today Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In the code: 3309 if ( C4::Context->preference('NoRenewalBeforePrecision') eq 'date' 3310 and $issuing_rule->{lengthunit} eq 'days' ) 3311 { 3312 $soonestrenewal->truncate( to => 'day' ); 3313 } 3314 return $soonestrenewal if $now < $soonestrenewal; We truncate soonest renewal, so when it matches todays date line 3314 compares Today at 00:00:00 to Today at (time renewal checked) So we don't return soonest renewal, but fall back to $now - which does allow renewal, but is not technically correct -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44

[Bug 16117] New: Feature request: Log borrower cardnumbers and item barcodes which are not valid
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '24

12 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16117 Bug ID: 16117 Summary: Feature request: Log borrower cardnumbers and item barcodes which are not valid Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com On any circ screen where a barcode could be scanned (circ.pl, checkin.pl, checkout and return boxes), we should have the option of logging failed barcode scans, for the purpose of trouble-shooting. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 44

[Bug 17337] New: waitingreserves.pl should trigger transfers as well as holds
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '24

11 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17337 Bug ID: 17337 Summary: waitingreserves.pl should trigger transfers as well as holds Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 17010 addresses triggering the next hold when a hold is cancelled, but transfers should also be triggered. Currently in 3.22.8 nothing happens. It is unclear if 17010 addresses transfers as well. Also, in 3.18 local holds were spotty when holds were triggered. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 32593] New: Item search option location breaks with only one location defined
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '24

09 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32593 Bug ID: 32593 Summary: Item search option location breaks with only one location defined Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor 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 When there is only one location (LOC) configured, the search option for locations on item search is not generated correctly. It shows the 'all locations' option and then 3 empty (no description) entries: <select id="location" name="location" multiple="multiple" size="4"> <option value="" selected="selected"> <span>All locations</span> </option> <option value="REF"></option> <option value="Reference"></option> <option value="Reference"></option> </select> As soon as a second location is configured, the list will be generated correctly. To test: * delete all LOC entried, but one, I left REF in the sandbox * Go to item search * Verify that only 'all locations displays' with 3 clickable empty entries below * Add another LOC entry * Verify the list now works again -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 33842] New: Search for authid not returning right results with QueryAutoTruncate ON
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '24

09 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33842 Bug ID: 33842 Summary: Search for authid not returning right results with QueryAutoTruncate ON Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: adolfo.rodriguez(a)xercode.es Conditions to replicate this bug: 1) Preference QueryAutoTruncate activated 2) Have authorities with low authids 3) ElasticSearch, though it should also happen with Zebra. You can try it on this demo, it's on the master branch. Intranet: https://intranet.koha-community.es OPAC: https://catalog.koha-community.es/ User demo/demo The following searchs return different results: 1) Search in the catalog an:1 The QueryAutoTruncate adds * so it returns all the biblios that use authorities with authids that begin with 1, which are 81. That doesn't make sense as those authorities have nothing in common. https://intranet.koha-community.es/cgi-bin/koha/catalogue/search.pl?q=an%3A1 2) The authority with the id 1 is Mika Ninagawa, if you search her in the Authorities module, it says the authority is being used in two records, which is correct. https://intranet.koha-community.es/cgi-bin/koha/authorities/authorities-hom… 3) In the authority detail, Koha makes the same query as in point 1 so it appears it's being used in 81 records. https://intranet.koha-community.es/cgi-bin/koha/authorities/detail.pl?authi… I think this disparity in results can be confusing for librarians and readers, as they won't understand why Koha is recovering records that are unrelated to the author/subject... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 26978] New: Add item type criteria to batch extend due date tool
by bugzilla-daemon＠bugs.koha-community.org 09 Feb '24

09 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26978 Bug ID: 26978 Summary: Add item type criteria to batch extend due date tool Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org In the Change due date plugin by inLibro, there is a possibility of choosing specific item types to extend due dates. I think the original purpose of the batch extend due date tool was for COVID and the purpose was to extend everything regardless, as the libraries were closed. However, it would be nice if we could discontinue de plugin in favour of the native tool. But that would require that the native tool have all the options that the plugin has. https://inlibro.com/en/changeduedate-instructions/ One example of use case would be where a school would want to extend loans for textbooks, because the semester was extended, but not the other types of items. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 32166] New: When adding to a basket from a staged file we may use the wrong inputs
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '24

08 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32166 Bug ID: 32166 Summary: When adding to a basket from a staged file we may use the wrong inputs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org On addorderiso2709.pl we loop over the records in the staged batch: for my $biblio (@$biblios){ $biblio_count++; skipping any not selected, which inlcudes any already imported: next if not grep { $_ eq $$biblio{import_record_id} } @import_record_id_selected; Later we use that count to find the inputs: my @homebranches = $input->multi_param('homebranch_' . $biblio_count); The problem being that if a record is already imported, our count increases, but the input on the page still counts from 1 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 29930] New: Auth with LDAP: Update tag leads to unwanted updates
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '24

08 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29930 Bug ID: 29930 Summary: Auth with LDAP: Update tag leads to unwanted updates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: janik.hilser(a)systemli.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I have observed that as soon as the update tag is set to true in koha-config.xml, the cardnumber is also updated on every login, even if it is not in the mappings. After a login the cardnumber is equal to the userId, but according to log entries it is empty in between. I could see this in the log entry that is generated in line 214 of the Auth_with_ldap.pm. Maybe line 262 of the same file has something to do with it? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42

[Bug 33170] New: Refactor MarcItemFieldsToOrder code to make adding more field simpler
by bugzilla-daemon＠bugs.koha-community.org 08 Feb '24

08 Feb '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33170 Bug ID: 33170 Summary: Refactor MarcItemFieldsToOrder code to make adding more field simpler Change 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org There is no need for this code to have a hard coded list of fields directly in the code. Any invalid keys would be skipped anyway. If we refactor this code then adding new fields will be much simpler. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22