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

[Bug 20948] New: Hold requests on detail.pl
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '20

10 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20948 Bug ID: 20948 Summary: Hold requests on detail.pl Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The next hold request showing on the detail.pl page next to items is useless and should be removed or fixed. The information for requests on an item is misleading. It shows the next item level hold rather than showing the next hold it will fulfill. I understand how this might be useful in some obscure circumstances, but for the most part it leads staff to believe that this is the next hold it will fill, and that is not the case. Case in point...we have a new item, only one in the collection. 33 next available holds, and 1 item level hold at the very end of the list, going to a different library. With all the other holds ahead of it, and the fact that we have local holds priority enabled, this looks very wrong, and leads staff to confusion and panic. It might be helpful to some libraries to see that there is a specific hold on a particular item, but around here, most libraries will view this as misleading. There should be a setting to change the behavior, or turn it off. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 45

[Bug 15972] New: Make it possible to include additional title information in notices (such as 245$b)
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '20

10 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15972 Bug ID: 15972 Summary: Make it possible to include additional title information in notices (such as 245$b) 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org For some titles the 245$a (MARC21) is not specific enough and it would be necessary to include the 245$b information in the notices, that is currently not mapped in the database. Apart from 245$b (remainder of title) other information like 245$n/$p for volumes would be nice to have. This was reported by a library using serial claims - where the title is often the same and the correct serial can only be identified with the help of additional information. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 17854] New: Print Slip and Close button
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '20

04 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17854 Bug ID: 17854 Summary: Print Slip and Close button Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Would like to see an enhancement on the clear screen (X) button on patron records. It would be great if it were replaced with a button with preference settings that would have the following options: Close Print Slip and Close Print Quick Slip and Close It would also be great if it could have a side action arrow giving you access to the other options that are not defaulted. This feature would help with staff closing accounts (clearing screen) when done, and making slip printing stand out a little better. It would also be a streamlined workflow. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 17532] New: koha-shell does not propagate the error code
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '20

01 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17532 Bug ID: 17532 Summary: koha-shell does not propagate the error code Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal 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 26

[Bug 20624] New: Allow switching off the OAuth2 client credentials grant
by bugzilla-daemon＠bugs.koha-community.org 01 Jun '20

01 Jun '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20624 Bug ID: 20624 Summary: Allow switching off the OAuth2 client credentials grant Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 18330] New: REST API: Date-time handling
by bugzilla-daemon＠bugs.koha-community.org 29 May '20

29 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18330 Bug ID: 18330 Summary: REST API: Date-time handling Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Swagger2 wants dates and date-times as defined in RFC3339, https://xml2rfc.tools.ietf.org/public/rfc/html/rfc3339.html#anchor14 Make sure each object property has a format date or date-time defined where needed. We should include information on time zone and use an appropriate separator "T" between date and time, e.g.: 2017-03-24T14:00:00+02:00 2017-03-24T12:00:00Z -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 18674] New: Show timezone for Perl and MySQL on the About Koha page
by bugzilla-daemon＠bugs.koha-community.org 28 May '20

28 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18674 Bug ID: 18674 Summary: Show timezone for Perl and MySQL on the About Koha page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: nengard(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org With the pushing of Bug 18299, we no longer have a quick way of checking the timezone of the Perl and MySQL connection. We should add some code to the About Koha page to show this info. -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 19197] New: Lower case "or" results in broken ElasticSearch queries
by bugzilla-daemon＠bugs.koha-community.org 28 May '20

28 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19197 Bug ID: 19197 Summary: Lower case "or" results in broken ElasticSearch queries Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In some places a literal "or" is used to build search queries which probably works with Zebra, but not with ElasticSearch. Replacing theses occurrences fixes the problem in those cases. This is just a band aid, not addressing the real issue which is (I guess) that a query abstraction interface is needed, and zebra-specific syntax should not be used directly in search queries, but this will at least solve this particular issue. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 21446] New: Permanent location should show with cart location - course-details.pl
by bugzilla-daemon＠bugs.koha-community.org 27 May '20

27 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21446 Bug ID: 21446 Summary: Permanent location should show with cart location - course-details.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Continuing location fixes in modules. Adding permanent location in course-details.pl. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 20211] New: Guarantor/Guarantee and PayPal development ideas
by bugzilla-daemon＠bugs.koha-community.org 26 May '20

26 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20211 Bug ID: 20211 Summary: Guarantor/Guarantee and PayPal development ideas Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jesse(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org 1. Add ability for a guarantor to see fines on their guarantee's accounts in the OPAC 2. Add ability for a guarantor to pay fines on their guarantee's accounts via PayPal in the OPAc (once #1 is complete) 3. Add ability to set a mimimum payment threshold when using PayPal - i.e. the "Make payment" button is not active until the "Amount to pay:" amount is greater than the amount specified in the threshold 4. Add the ability for the PayPal threshold to be set on a branch-by-branch basis (i.e. put it on the Circulation and fines rules rules page for the patron's home library) 5. Add the ability to turn off PayPal if a single branch doesn't want their patrons to use it (i.e. put something on a library's Circulation and fines rules rules that allows that library to prevent patrons with that library's home branch from using PayPal) -- You are receiving this mail because: You are watching all bug changes.

1 14