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

[Bug 17841] New: Can't use indexname "acqdate, st-date-normalized" in keyword search
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '22

01 Apr '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17841 Bug ID: 17841 Summary: Can't use indexname "acqdate,st-date-normalized" in keyword search Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org It is possible to search for acquisition date from the advanced search in staff. But if you try to use the index name for an 'expert search' in the keyword search field, no results will come up. Example: Advanced search > acquisition date: 2016-12* (or whatever works for you) This should give correct results. Enter acqdate,st-date-normalized: 2016-12* into the keyword search - no results will appear. Something seems to be missing in order to make it possible to construct the same search manually. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 18846] New: Fund list on 'aquisitions statistics' page shows wrong values
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '22

30 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18846 Bug ID: 18846 Summary: Fund list on 'aquisitions statistics' page shows wrong values Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org To test: - Create a budget with some funds - Duplicate the budget - You should now have 2 budgets with the same fund codes and descriptions for each - Check the fund list on the reports > aquisitions statistics page - Verify the list looks correct - you should see all funds once - Alter the description of one of your funds and save - Check the fund list again after reloading the page: The changed fund will appear "doubled up" with the same (old or new) description -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 17648] New: ACCTDETAILS notice does not show in notices.pl
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '22

25 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17648 Bug ID: 17648 Summary: ACCTDETAILS notice does not show in notices.pl 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The ACCTDETAILS notice apparently bypasses message_queue; notices are sent directly to the linux mail queue. This may be useful from the standpoint that the message is sent immediately, but it should still be added to message_queue with status='sent', so that it's available when looking at the borrowers notices. --Barton -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 20362] New: Direct link to authority records missing in staff detail view (1xx, 7xx)
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '22

25 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20362 Bug ID: 20362 Summary: Direct link to authority records missing in staff detail view (1xx, 7xx) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Add a link to the authority record from the detail patch for authors and contributors (1xx, 7xx) like they exist in the staff page and like it's implemented for subjects on bug 16427. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 19171] New: Confusing message "no items available" on the holds page
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '22

24 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19171 Bug ID: 19171 Summary: Confusing message "no items available" on the holds page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When there are no items available to be placed on hold, the hold page in the OPAC reads for example: Sorry, none of these items can be placed on hold. No items available. To the patron this is confusing: - the record has items, but they are not showing (none of these...?) - the record may well have available items that are not shown, as a lot of libraries don't allow holds on items that are available. I think we could improve this already by rephrasing the message a bit. -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 20442] New: Use more HtmlTags filter
by bugzilla-daemon＠bugs.koha-community.org 23 Mar '22

23 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20442 Bug ID: 20442 Summary: Use more HtmlTags filter Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Some strings are hard to translate, because there are HTML tags splitting the sentences into multiple parts. Use the HtmlTags filter so the sentences can be translated as a single unit instead. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 21594] New: description in api_keys table needs a DEFAULT value
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '22

22 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21594 Bug ID: 21594 Summary: description in api_keys table needs a DEFAULT value 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 21597] New: Test suite is still failing with new default SQL modes
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '22

22 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21597 Bug ID: 21597 Summary: Test suite is still failing with new default SQL modes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 20521, 20144 We pushed bug 20521 to enable the problematic SQL modes for dev installs, and now new tests (since bug 20144 has been pushed) are failing. Let's fix them again. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20144 [Bug 20144] Test suite is failing with new default SQL modes https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20521 [Bug 20521] dev installations should run with problematic SQL modes -- You are receiving this mail because: You are watching all bug changes.

1 46

[Bug 20076] New: Overdues: remove redundant message when patrons don't have email addresses
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '22

18 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20076 Bug ID: 20076 Summary: Overdues: remove redundant message when patrons don't have email addresses 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: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org When running overdue_notices.pl, one email message is sent to the library containing all the print versions of the related notices. But since a past enhancement, one message of the type print also is created for each of such notices. So now we have two print overdue notice generations. Which is why the email message is not longer relevant as it's superseded by the individual and ready to print messages. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 56

[Bug 21648] New: Patron Merge needs more flexibility and transparency
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '22

16 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21648 Bug ID: 21648 Summary: Patron Merge needs more flexibility and transparency Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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 The patron merge tool introduced in 18.05 is a great step, but creates some issues. Contact information for the discarded patron is lost even when the kept patron has null values for those fields. Merging patrons with additional patron attributes results in a patron with multiple values for an attribute that is not supposed to be repeatable. The screen that confirms the merge has completed reports counts of transferred data but doesn't allow one to see details of what was transferred from the discarded patron to the kept patron. A good next step here would be an interface similar to what we see when merging bibs -- the opportunity to see values for both patron records and select which will be carried forward to the final record, at least for all fields in the borrowers table and for additional patron attributes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34