July 2017 - Koha-bugs - lists.koha-community.org

[Bug 18495] New: Creating a subgroup within report doesn' t add report to that group
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '23

24 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18495 Bug ID: 18495 Summary: Creating a subgroup within report doesn't add report to that group Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org You can create a subgroup while editing/creating a report, but it doesn't add the report to that group. I didn't test if this is the case with the report group. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 17987] New: Changing PatronSelfRegistrationDefaultCategory to a dropdown menu syspref
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '23

23 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17987 Bug ID: 17987 Summary: Changing PatronSelfRegistrationDefaultCategory to a dropdown menu syspref Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleishaamohia(a)hotmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Rather than a free text syspref where a user can easily put in a category that doesn't exist. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 18805] New: Add ability to use up account credits
by bugzilla-daemon＠bugs.koha-community.org 03 Feb '23

03 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18805 Bug ID: 18805 Summary: Add ability to use up account credits 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Blocks: 14825 Right now, in Koha, credits always have a static amount outstanding. So if a patron owes $10 in fines, and has a $10 credit, they technically owe nothing, but yet they still owe $10. This seems rather confusing. Instead, we should add the ability for credits to be used to pay down closed out fines and other fees. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14825 [Bug 14825] Accounts Rewrite Omnibus -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 65

[Bug 18506] New: Shibboleth SSO Only Mode
by bugzilla-daemon＠bugs.koha-community.org 01 Feb '23

01 Feb '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18506 Bug ID: 18506 Summary: Shibboleth SSO Only Mode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Shibboleth works at it's best when it is the ONLY form of authentication allowed on the system. That way, if you disable opacPublic you can have a system that automatically redirects the user to the IdP for authentication immediately and skips any other forms of authentication leading to a more seamless SSO solution. -- You are receiving this mail because: You are watching all bug changes.

1 79

[Bug 15797] New: C4::Koha::GetKohaImageurlFromAuthorisedValues is no longer in use
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '23

30 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15797 Bug ID: 15797 Summary: C4::Koha::GetKohaImageurlFromAuthorisedValues is no longer in use 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(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Blocks: 15779 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15779 [Bug 15779] Remove unnecessary parts of C4::Koha -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 17252] New: Koha::AuthorisedValues - Remove GetAuthorisedValueByCode
by bugzilla-daemon＠bugs.koha-community.org 30 Jan '23

30 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17252 Bug ID: 17252 Summary: Koha::AuthorisedValues - Remove GetAuthorisedValueByCode 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(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 18084] New: Language selector hidden in user menu on mobile interfaces
by bugzilla-daemon＠bugs.koha-community.org 26 Jan '23

26 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18084 Bug ID: 18084 Summary: Language selector hidden in user menu on mobile interfaces Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 If you choose to have the language selection at the top, it will be hidden in the 'user menu' on smaller display sizes. That seems a bit counter-intuitive as you wouldn't expect it there. It would be nice if it was visible at all times. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 15765] New: Request to replace patron number list by patron barcode list
by bugzilla-daemon＠bugs.koha-community.org 25 Jan '23

25 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15765 Bug ID: 15765 Summary: Request to replace patron number list by patron barcode list Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: Heinrich.Hartl(a)email.de QA Contact: testopia(a)bugs.koha-community.org Change request: Substitute patron barcodes for patron numbers Patron card creator is working with something called a batch. A batch is a list of patron numbers where patron number is the koha internal index of a patron. Unfortunately the patron number is to my knowledge a patron property that is not known elsewhere. E.g. it is not shown when displaying patron details. But even in the patron search part of patron card creator that number is not shown. In the patron search we see e.g. name and barcode of the patron. Patron barcodes are familiar and found in many reports, in patron import and in patron displays. I suggest to replace the list of patron numbers by a list of patron barcodes. Patron barcodes are also unique identifers of patrons, an unambigous index into the borrowers table. An entered barcode not necessarily identifies an existing patron. However an entered patron number is not more reliable since a patron may have been deleted or may not be existent. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 17084] New: Nightly build bot bug
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '23

19 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17084 Bug ID: 17084 Summary: Nightly build bot bug Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Things the nightly build bot says. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 149

[Bug 18186] New: Amounts with decimal comma instead of decimal dot breaking payments
by bugzilla-daemon＠bugs.koha-community.org 16 Jan '23

16 Jan '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18186 Bug ID: 18186 Summary: Amounts with decimal comma instead of decimal dot breaking payments Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In our current installations running under Plack, the amounts on the pay and paycollect pages suddenly started showing with a decimal comma instead of a decimal point. This causes quite a bit of trouble, as Koha expects a . and amounts entered didn't result in the expected payments. We got several reports about payments being broken in Koha. Test plan: - Add manual invoice - View the "fines" tag - Verify that individual fees and totals display with , instead of . - Pay selected or any amount - Verify that the input field for the amount is also showing the , - Verify that paying something like 1,10 doesn't work as expected. The problem with the test plan is, that you might not see the ,. This appears only on our productions servers, but not in my development environment. We tested: - different language settings in Koha - different language settings in the browser - verified that CurrencyFormat isn't used in the code on those page - verified that all the formatting done was using the TT filter format('%.2f') In the end the problem turned out to be related to Plack. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16