May 2022 - Koha-bugs - lists.koha-community.org

[Bug 20235] New: Telegram notifications
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '22

21 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20235 Bug ID: 20235 Summary: Telegram notifications Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Create a Koha Telegram Bot to send notifications via Telegram instant messaging app. Telegram is a popular instant messaging application alternative to WhatsApp. Telegram has an API for writing bots that interact with users. This could be used to send Koha's notifications for free directly into patron's Telegram app. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 29496] New: can't save an order with mandatory items subfields
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '22

21 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29496 Bug ID: 29496 Summary: can't save an order with mandatory items subfields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org Here is the plan to reproduce it : - Unimarc flavour - Items in 995 field whith 3 mandatory / > Tab:10, | Koha field: items.homebranch, Not repeatable, Mandatory, Not Important, | Auth value:branches, > Tab:10, | Koha field: items.holdingbranch, Not repeatable, Mandatory, Not important, | Auth value:branches, > Tab:10, | Koha field: items.location, Not repeatable, Mandatory, Not important, | Auth value:LOC, - AcqCreateItem="placing an order" When adding an order from a new empty record,I filled - the title - the 3 mandatory items subfields (and clicked on add item) - the fund - the currency - the vendor price - the tax rate - the discount - the retail price - the replacement cost - the budgeted cost - the total When saving, I have the message : "Form not submitted because of the > following problem(s): - 3 item mandatory fields empty". You can try here : http://staff-master.sandboxes.ptfs-europe.co.uk/cgi-bin/koha/acqui/basket.p… Sonia -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 30842] New: Two-factor authentication code should be valid longer
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '22

21 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30842 Bug ID: 30842 Summary: Two-factor authentication code should be valid longer Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Authentication Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Depends on: 28787 So far it's valid only 30 second, it should be extended. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28787 [Bug 28787] Send a notice with the TOTP token -- You are receiving this mail because: You are watching all bug changes.

1 20

[Bug 18217] New: SMS alert number should be grouped with other borrower contact information.
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '22

21 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18217 Bug ID: 18217 Summary: SMS alert number should be grouped with other borrower contact information. 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: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com SMS alert number is currently grouped with borrower messing preferences. This is inconsistent with the rest of the borrower contact information. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 30811] New: Allow hold pickup location to default to item home/holding branch for bib-level holds
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '22

21 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30811 Bug ID: 30811 Summary: Allow hold pickup location to default to item home/holding branch for bib-level holds 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 23659 Bug 23659 adds the ability to make item-level holds default their pickup location to either the item homebranch or the item holdingbranch. It would be great to be able to do this for bib-level holds, too -- that would mean the hold does not truly have a pickup branch until an item is captured, at which point the pickup location gets set to wherever the captured item is. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23659 [Bug 23659] Allow hold pickup location to default to item home branch for item-level holds -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 30855] New: Rename /import => /import_batches
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '22

21 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30855 Bug ID: 30855 Summary: Rename /import => /import_batches Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com CC: tomascohen(a)gmail.com It will keep things more consistent once we add routes to deal with import batches. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 15996] New: Bibliographic records diffing tool
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '22

21 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15996 Bug ID: 15996 Summary: Bibliographic records diffing tool Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently there is no tool to diff differences or changes between biblios or their different versions. This is most useful for logging who changed and what. This feature introduces a biblio diffing module, which takes an arbitrary amount of MARC::Records and produces a complex data structure about all the identified changes. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 30774] New: Typo: i %sEdit %sReserve %s
by bugzilla-daemon＠bugs.koha-community.org 21 Jun '22

21 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30774 Bug ID: 30774 Summary: Typo: i %sEdit %sReserve %s Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: trivial Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The single i here seems misplaced: koha-tmpl/intranet-tmpl/prog/en/modules/course_reserves/add_items-step2.tt:33 i %sEdit %sReserve %s -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 28959] New: virtualshelves.category is really a boolean
by bugzilla-daemon＠bugs.koha-community.org 20 Jun '22

20 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28959 Bug ID: 28959 Summary: virtualshelves.category is really a boolean Change sponsored?: --- Product: Koha Version: unspecified 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 Somehow it got more complicated than required. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 61

[Bug 30361] New: If bug 29369 is applied or an update to 21.11.03 occurs no item saving is permitted if the framework marks this field as mandatory.
by bugzilla-daemon＠bugs.koha-community.org 19 Jun '22

19 Jun '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30361 Bug ID: 30361 Summary: If bug 29369 is applied or an update to 21.11.03 occurs no item saving is permitted if the framework marks this field as mandatory. Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: courtenay.johnson(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When I upgraded from 21.05.03 to 21.11.03 I found when adding an item using the book framework it would refuse to save the net item. It instead displayed a popup that stated a mandatory field was blank. It does not provide any visual indication as to which field is the problem. (I have 6 visible mandatory fields) I determined that the specific field that was causing the problem had the dateaccessioned.pl plugin and is the 952$d. The date picker does generate a date which looks normal, but the item just can’t be saved. When I edited the framework to make this field not mandatory, then I can save newly created or edited items. The date in the picker is shown correctly in the display of the saved item. In 21.05.03 there was no problem. I read bug 29369 and examined the code and this had been applied in 21.11.03. The workaround is totally acceptable to me and works fine with no other issue noticed so far. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1