February 2019 - Koha-bugs - lists.koha-community.org

[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 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 20570] New: Add script to complete scanned article requests
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '22

04 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20570 Bug ID: 20570 Summary: Add script to complete scanned article requests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 20689] New: make sure the extra subfields are in a search index
by bugzilla-daemon＠bugs.koha-community.org 04 Mar '22

04 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20689 Bug ID: 20689 Summary: make sure the extra subfields are in a search index Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, when you add a new subfield in a marc bibliographic framework and that subfield is not in the marc format normally, you can not add it as a item search fields. It would be useful to be able to use these new subfields for item search for exemple. Thanks, Patrick. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 85

[Bug 18543] New: Automated emails for new patron accounts with the AutoEmailOpacUser preference
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '22

01 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18543 Bug ID: 18543 Summary: Automated emails for new patron accounts with the AutoEmailOpacUser preference Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: karen(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When the AutoEmailOpacUser preference is set to Send, Koha should send an email with account details to newly created patrons. After some testing, we discovered that Koha will only send emails to patrons if the username and password are entered into the system by hand. The email is not sent when the username and password are automatically generated by the system. The expected behavior is that Koha would send the account details email to newly created patrons when the system automatically generates the username and the password. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 21968] New: Don't make it possible to put a return date prior to the loan date with SpecifyReturnDate
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '22

28 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21968 Bug ID: 21968 Summary: Don't make it possible to put a return date prior to the loan date with SpecifyReturnDate Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, when te system preference SpecifyReturnDate is activate, you can put a return date prior to the loan date and it is not logical. It would be nice if the possibility to enter a previous date will be block or a message tells us that this return date is before the date of the loan. Regards, Patrick. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 19800] New: confusion with the notification for an item "in transfer" during a check-in
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '22

25 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19800 Bug ID: 19800 Summary: confusion with the notification for an item "in transfer" during a check-in Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hi, When we receive a items in transfer, we have two option. We can cancel the transfer with te fonction "Tranfers to receive" or we can do a check-in. But, the notification the notification that appears is confusing. Indeed, in this notification it is written taht the item is "Not Checked out.". The message is misleading because that could be perceived as if the check-in had not worked the first time. The message should be like "Item in transit - now available" or "Item returned from transit - Now available". Like this, the notification would no longer be confusing for library staff. Patrick. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 20609] New: Get back the "Add order to basket" on the basket page
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '22

25 Feb '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20609 Bug ID: 20609 Summary: Get back the "Add order to basket" on the basket page Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, Before the 16.11 version of Koha, when we opened a basket we had acces to the form "Add order to basket". Now we have to clik on "add to basket". This form was convenient and avoided an extra click. It could be nice to have this form directly from the basket without havind to do an extra clic. Patrick. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1