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

[Bug 22534] New: Add ability to choose which fields are copied from guarantor to guarantee
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '21

25 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22534 Bug ID: 22534 Summary: Add ability to choose which fields are copied from guarantor to guarantee Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: genevieve.beaudry(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- When linking a guarantee to a guarantor, some fields are automatically copied, such as the address, the phone number, etc. I suggest that a system preference be added so that the system administration can choose which fields they want to be copied. By default, it can stay address and phone number, but they would have the possibility to remove those. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 24603] New: Allow to cancel charges in patron accounting
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '21

25 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24603 Bug ID: 24603 Summary: Allow to cancel charges in patron accounting Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org There is already a button to void a payment. It should be possible to cancel a charge too. -- You are receiving this mail because: You are watching all bug changes.

1 63

[Bug 27850] New: Search link for 260 a and c in MARC21 XSLT dispay
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '21

25 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27850 Bug ID: 27850 Summary: Search link for 260 a and c in MARC21 XSLT dispay 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: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In MARC21 XSLT display, 260$b is a search link on 'Provider'. $a and $c also have a search field, we can create search links. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 28563] New: Add AllowHoldItemTypeSelection to HEA
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '21

25 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28563 Bug ID: 28563 Summary: Add AllowHoldItemTypeSelection to HEA Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This syspref is missing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 27583] New: Clarify how cash management fits together
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '21

25 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27583 Bug ID: 27583 Summary: Clarify how cash management fits together Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The new(ish) cash management options in Koha aren't clearly defined... you can enable parts of the system without enabling all of it. We should try to clarify the module by more clearly defining how it fits together. I propose to add a 'Cash management' heading under 'Tools' to move the 'Cashuup registers' option to and renaming some of the interface area's to better clarify their purposes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 28380] New: Elasticsearch - correct 024aa in mappings
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '21

25 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28380 Bug ID: 28380 Summary: Elasticsearch - correct 024aa in mappings 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: caroline.cyr-la-rose(a)inlibro.com In the mappings.yaml file, under the identifier-other index, the field 024aa is listed. I don't know if the double a can cause a problem, or if it's simply a typo without consequence. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 28660] New: Self checkout is not automatically logging in
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28660 Bug ID: 28660 Summary: Self checkout is not automatically logging in Change sponsored?: --- Product: Koha Version: 21.05 Hardware: Other OS: Linux Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jhenderson(a)nsd.org QA Contact: testopia(a)bugs.koha-community.org The self-checkout is not automatically logging in with the staff username and password provided. Upon entering the URL for the self-checkout system, it is still prompting for the staff username and password. This a fresh install of Koha 21.05 on Debian 10. No errors during installation. Things I have done to ensure everything would work: - I have created a patron account with the self-check modules turned on for this patron and the username and password is listed in the system preferences under AutoSelfCheckAllowed, and that is turned to allow. - The selfcheck is enabled This is either a bug or something that I am not seeing -- You are receiving this mail because: You are watching all bug changes.

1 42

[Bug 17775] New: blocker of bug 7172
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17775 Bug ID: 17775 Summary: blocker of bug 7172 Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: mnashbat(a)alfaisal.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Koha & ldap authentication fail authenticating new users when enabling plack, it works fine only if plack is desabled. Ldap authentication works fine with old registered users. -- You are receiving this mail because: You are watching all bug changes.

1 34

[Bug 29264] New: SIP config allows use of non-branchcode institution ids causes workers to die without responding
by bugzilla-daemon＠bugs.koha-community.org 24 Nov '21

24 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29264 Bug ID: 29264 Summary: SIP config allows use of non-branchcode institution ids causes workers to die without responding Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If is entirely possible to create an SIP institution whose ID does not match a valid branchcode in Koha's SIP config. In fact, Koha's example SIP config contains an example of this ( kohalibrary / kohalibrary2 ). If a SIP login uses an institution with an id that doesn't match a valid branchcode, everything will appear to work, but the SIP worker will die anywhere that Koha gets the branch from the userenv and assumes it is valid. The repercussions of this are that actions such as the checkout message simply die and do not return a response message to the requestor. At the very least, we should output a warning to the SIP log. I think we should strongly consider disallowing institution ids in the SIP config that do not match valid branchcodes. In this scenario, attempting to start the SIP server should result in a error message with the SIP server exiting immediately. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 19444] New: Automatic renewal script should not auto-renew if a patron' s record has expired
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '21

23 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19444 Bug ID: 19444 Summary: Automatic renewal script should not auto-renew if a patron's record has expired 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: janet.mcgowan(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently with the automatic_renewals.pl script, materials are still auto-renewed even if the patron's account has expired. The automatic renewals script has error conditions which prevent automatic renewals in these circumstances: $error eq 'too_many' or $error eq 'on_reserve' or $error eq 'restriction' or $error eq 'overdue' or $error eq 'auto_too_late' or $error eq 'auto_too_much_oweing' or $error eq 'auto_too_soon The error conditions should take into account the expiry date of borrower and not auto renew if the borrower's account has expired. For example adding a new error code such as 'borrower_expired' - or whatever convention achieves this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38