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

[Bug 25616] New: Uppercase hard coded lower case boolean operators for Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '22

20 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25616 Bug ID: 25616 Summary: Uppercase hard coded lower case boolean operators for Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com Since valid boolean operators in the Elasticsearch mini language for Query String Queries needs to be upper case, there some occurrences of queries in Koha left that needs changing. I think I found most of them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 44

[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 21811] New: Add warning when order receive form is saved without entering 'quantity received'
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '22

18 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21811 Bug ID: 21811 Summary: Add warning when order receive form is saved without entering 'quantity received' Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement 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 A common mistake in training the acquisition module is that the 'quantity received' field is not changed before saving the order receive form. There is no warning or other indication, that this field is needed in order to make the receive happen. I think usability woudl be better with a visual clue or warning there. I am not sure if the field coudl be made mandatory. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 21866] New: Warning: This *report* was written for an older version of Koha. Run at your own risk.
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '22

17 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21866 Bug ID: 21866 Summary: Warning: This *report* was written for an older version of Koha. Run at your own risk. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We are always referring to reports, but this message can, in fact, be displayed for any/all plugins.. we should replace 'report' with 'plugin'. -- You are receiving this mail because: You are watching all bug changes.

1 19

[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

[Bug 23499] New: Show subtitle in serials search
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '22

15 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23499 Bug ID: 23499 Summary: Show subtitle in serials search Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When viewing search results on serials-search.pl, we only see biblio.title. This gets quite confusing when titles like: American economic journal. Microeconomics American economic journal. Macroeconomics American economic journal. Economic Policy and so forth. It'd be great to pull more of the 245 into this screen. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 25710] New: On ElasticSearch only system zebraqueue table is never purged
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '22

15 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25710 Bug ID: 25710 Summary: On ElasticSearch only system zebraqueue table is never purged Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 21820, 16248 Even if there's no zebra server zebraqueue table is populated (with done == 0). misc/cronjobs/cleanup_database.pl is only deleting zebraqueue table with done == 1 But without a zebra indexer daemon nothing is setting zebraqueue.done to 1. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16248 [Bug 16248] ModZebra doesn't update zebraqueue if ES is enabled https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21820 [Bug 21820] Zebraqueue should not be added to -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19642] New: If autoMemberNum is enabled, we should just ignore cardnumber entry in BorrowerMandatoryField
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '22

10 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19642 Bug ID: 19642 Summary: If autoMemberNum is enabled, we should just ignore cardnumber entry in BorrowerMandatoryField 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 19225 proposes a warning for users that the config is wrong. I propose instead, we should just ignore that field if automembernum is enabled (since it autocalculates and becomes mandatory -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 20336] New: Add a generic way for Koha::Object(s) to call logaction as required
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '22

09 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20336 Bug ID: 20336 Summary: Add a generic way for Koha::Object(s) to call logaction as required 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 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 23091] New: Restore Forgiven Overdue Fines When Lost Item Returned
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '22

09 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23091 Bug ID: 23091 Summary: Restore Forgiven Overdue Fines When Lost Item Returned Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Bug 22877 is closing a loophole that several libraries have been happily using to achieve their desired fine behavior. These libraries want this behavior: - item accrues overdue fine up to maximum - when item is lost, overdue fine is forgiven and lost fee is applied - when item is returned, lost fee is forgiven and overdue fine is restored So, while many libraries will see bug 22877 as a fix, for some libraries it will be a very big disruption. My understanding of bug 22877 is that we're changing the fine calculation at checkin to not do anything with fines if the item is lost. Maybe we need to instead say don't add fines if the item is lost and the there is an existing fine for that issue where amountoutstanding!=0? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 225