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

[Bug 24147] New: Objects.t is failing randomly
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '21

04 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24147 Bug ID: 24147 Summary: Objects.t is failing randomly Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Not confirmed yet, bug on the newly created job Koha_Master_D9_MDB_Latest, there is the following failure (run 2): koha_1 | # Failed test 'Koha::Objects->search_related should work as expected' koha_1 | # at t/db_dependent/Koha/Objects.t line 145. koha_1 | # got: 'dxdYyUDoA' koha_1 | # expected: 'hJnosHQGlA' koha_1 | koha_1 | # Failed test 'Koha::Objects->search_related should work as expected' koha_1 | # at t/db_dependent/Koha/Objects.t line 146. koha_1 | # got: 'hJnosHQGlA' koha_1 | # expected: 'dxdYyUDoA' koha_1 | koha_1 | # Failed test 'Koha::Objects->search_related should work as expected' koha_1 | # at t/db_dependent/Koha/Objects.t line 151. koha_1 | # got: 'dxdYyUDoA' koha_1 | # expected: 'hJnosHQGlA' koha_1 | koha_1 | # Failed test 'Koha::Objects->search_related should work as expected' koha_1 | # at t/db_dependent/Koha/Objects.t line 152. koha_1 | # got: 'hJnosHQGlA' koha_1 | # expected: 'dxdYyUDoA' koha_1 | # Looks like you failed 4 tests of 8. koha_1 | koha_1 | # Failed test 'search_related' koha_1 | # at t/db_dependent/Koha/Objects.t line 153. koha_1 | # Looks like you failed 1 test of 17. koha_1 | [19:23:01] t/db_dependent/Koha/Objects.t I do not recreate it locally, even after several restart of the db container. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 25464] New: Add ability to specify client IP and SIP account used in SIP2 logging
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '21

04 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25464 Bug ID: 25464 Summary: Add ability to specify client IP and SIP account used in SIP2 logging Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 CC: colin.campbell(a)ptfs-europe.com Bug 15253 originally had the ability to specify the incoming IP address used for a given log statement via SIP, as well as the SIP2 account that was in use at the time. This data is very helpful for debugging purposes, and should be brought back. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 25333] New: Change message transport type for Talking Tech from "phone" to "talkingtech"
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '21

03 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25333 Bug ID: 25333 Summary: Change message transport type for Talking Tech from "phone" to "talkingtech" 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org >From its inception, phone notices via Talking Tech have not behaved like other notices. Instead of reading notices generated by Koha, the Talking Tech scripts largely generate their own notices. We would like to pave the way to having "generic" phone notices that can be processed by plugins to support arbitrary telephony vendors ( we will be targeting Twilio initially ). To that end, it seems sensible to begin by changing the messaage transport type for Talking Tech from 'phone' to 'talkingtech' to highlight its specificity and difference from standard message transports. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 22206] New: Add route to handle holds suspensions
by bugzilla-daemon＠bugs.koha-community.org 03 Nov '21

03 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22206 Bug ID: 22206 Summary: Add route to handle holds suspensions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com Target Milestone: --- -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 43

[Bug 20168] New: update to bootstrap v4
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '21

02 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20168 Bug ID: 20168 Summary: update to bootstrap v4 Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: elias.dehler(a)thulb.uni-jena.de QA Contact: testopia(a)bugs.koha-community.org I'm currently working on updating the bootstrap template to bootstrap v4. This requires to update jQuery as well. My work is based on the current 17.11.02 koha release. I'm trying to keep the design as close to the current design as possible. At the moment i have nothing to show of my current process but as soon as everything plays nice i will post a link to my repository. The goal is to get a template based on the current version of bootstrap. -- You are receiving this mail because: You are watching all bug changes.

1 78

[Bug 19206] New: How should we sort 19xx when order is pubdate?
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '21

02 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19206 Bug ID: 19206 Summary: How should we sort 19xx when order is pubdate? 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org On bug 11046 I proposed to sort e.g. 19xx with 1900. This relates to the kohafield copyrightdate used to sort lists and in reports. For search results, the sort on publication date depends on pubdate as indexed by Zebra. If we add uncertain years like 19xx or better 19uu in the MARC21 008, they will be sorted after 1999 (current situation). We could add a "fix_008" in rebuild_zebra (just as a few other fixes already there) and replace 19uu by 1900 when indexing in order to get 19xx sorted with 1900. What do you think ? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 23321] New: Add 'tills' to the accounts system
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '21

01 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23321 Bug ID: 23321 Summary: Add 'tills' to the accounts system Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature 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 It would be helpful to track where money was taken/refunded from to enable an end of day procedure for tracking cash and other transactions. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 132

[Bug 24828] New: Add cash register support to SIP2
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '21

01 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24828 Bug ID: 24828 Summary: Add cash register support to SIP2 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 23321 Blocks: 13985 We add support for defining cash registers with bug 23321, however, these registers are currently only available for transactions via the staff client. We should also be able to add a register definition for a SIP client and assign transactions to it. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13985 [Bug 13985] Cash Management - Koha as 'Point of Sale' https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23321 [Bug 23321] Add 'cash registers' to the accounts system -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 23479] New: Hold cancellation confirmation too generic
by bugzilla-daemon＠bugs.koha-community.org 01 Nov '21

01 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23479 Bug ID: 23479 Summary: Hold cancellation confirmation too generic Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 cancellation confirmation should include the item title and the name of the person the hold was for. It is too easy to click on the wrong cancel button, and there is no knowing if you clicked the right one. We should not only be confirming the cancel action, but the data that is being cancelled. This goes for all types of confirmations throughout Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 19297] New: Standardize "can place hold" calculations
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '21

29 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19297 Bug ID: 19297 Summary: Standardize "can place hold" calculations Change sponsored?: --- Product: Koha Version: unspecified 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 There are several places where we need to know if a hold can be placed on a bibliographic record, or an item. And we also have several way of calculate it... Sometimes it is buggy, sometimes we calculate the information for nothing, sometimes it is done correctly. We need to make this calculation uniform in order to be consistent and always display the same and correct information everywhere. -- You are receiving this mail because: You are watching all bug changes.

1 10