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

[Bug 28513] New: Analytic search links formed incorrectly
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '21

10 Jul '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28513 Bug ID: 28513 Summary: Analytic search links formed incorrectly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In catalogue/detail.pl we form the analytics links like this: Host-item:$cleaned_title but that means we only search from Host-item field only the first token in the title, other tokens get searched from all fields. Same error is when forming the links to display in koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slim2intranetDetail.xsl -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 28615] New: Add a simple way to mock Koha::Logger
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '21

09 Jul '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28615 Bug ID: 28615 Summary: Add a simple way to mock Koha::Logger 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Now we are getting rid of $ENV{DEBUG} and C4::Debug with the correct use of Koha::Logger, we need an easy way to make sure we don't get problems with log permissions in the context of tests and, why not, being able to test those $logger->debug calls. -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 28595] New: Add ability to map preselected behavior to claims returned resolution statuses
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '21

09 Jul '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28595 Bug ID: 28595 Summary: Add ability to map preselected behavior to claims returned resolution statuses Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com Depends on: 28271, 28593, 28594 When resolving a claim, a library may or may not want to: - mark the item as returned (bug 28594) - apply a new lost status (bug 28271) - apply a new replacement fee (bug 28593) A great next step would be the option to map choices for those three variables to the various claim resolution options. So, for example, if the claim is resolved because the item was found in the stacks, then we want to mark it returned, forgive any fees, and not charge new fees. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28271 [Bug 28271] Add the ability to set a new lost status when a claim is resolved https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28593 [Bug 28593] Add ability to charge lost fee when applying new lost status when resolving a claim https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28594 [Bug 28594] Add ability to mark an item as retuned when resolving a claim -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 28588] New: Add Koha::Checkouts::ReturnClaim->resolve
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '21

09 Jul '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28588 Bug ID: 28588 Summary: Add Koha::Checkouts::ReturnClaim->resolve Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 Right now it is all solved in the controller. We need some low-level implementation that could be reused (cronjobs?) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 28591] New: debug pass to get_template_and_user but not used
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '21

09 Jul '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28591 Bug ID: 28591 Summary: debug pass to get_template_and_user but not used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org There is a "debug" parameter we are passing from the controller scripts to C4::Auth::get_template_and_user, but it's not actually used! -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 28590] New: get_shelves_userenv and set_shelves_userenv not used
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '21

09 Jul '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28590 Bug ID: 28590 Summary: get_shelves_userenv and set_shelves_userenv not used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We should remove them, the get is never used, and the set is storing info in userenv that is never read. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 28508] New: Use "Invoice number" instead of "Invoice no" on the invoice search filter
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '21

09 Jul '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28508 Bug ID: 28508 Summary: Use "Invoice number" instead of "Invoice no" on the invoice search filter 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org There is not much benefit to using "no" instead of "number", and it makes it less translateable and understandable. This should be fixed in three places that I can see: 1. the search filter form 2. the results table column heading 3. when there are no results, there is text that says 'Search was:' and a label that says 'Invoice no.' -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 27882] New: Move external search results links out of page heading
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '21

09 Jul '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27882 Bug ID: 27882 Summary: Move external search results links out of page heading Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 27740 When results are found in OverDrive, Recorded Books, or OpenLibrary collections the information is appended to the search results <h1>. I think the should be added just after the <h1> because they're not really part of the heading information. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27740 [Bug 27740] Accessibility: OPAC - Headings should have correct tags and hierarchy -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 26838] New: Improve styling of checkin message
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '21

09 Jul '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26838 Bug ID: 26838 Summary: Improve styling of checkin message Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 112596 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=112596&action=e… Checkin message box When an item type has a checkin message of the type "message" (rather than "alert"), the styling of the box is weird. The box is blue, but the background of the text is yellow. To replicate: 1) Go to Administration > Item types 2) Edit an item type and include a checkin message, the checkin message type should be "message" 3) Check in an item of that type I attached a screen capture of the blue/yellow message. In the manual, we can see what it used to look like : https://koha-community.org/manual/20.11/en/html/_images/itemtype-msg.png -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 15969] New: Allow use of Template Toolkit syntax for Phone Notices
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '21

09 Jul '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15969 Bug ID: 15969 Summary: Allow use of Template Toolkit syntax for Phone Notices Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org By allowing the use of Template Toolkit for generating the outgoing Talking Tech CSV files, we can give libaries more control over the data they send to Itiva. This enhancement would also make it possible to use the script for other services since the output is no longer fixed to a single format. -- You are receiving this mail because: You are watching all bug changes.

1 75