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

[Bug 18589] New: Show ILLs as part of patron profile
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '22

11 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18589 Bug ID: 18589 Summary: Show ILLs as part of patron profile 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 7317 adds a "Interlibrary loans" tab on the left hand side of patron details, under Purchase suggestions. But this behaves more like a link than a tab, taking you to the ILL module and a list limited to the patron in question. It would be better if this view looked more like a part of the patron details, with the tabs on the left hand side and the buttons on top. Compare this to the "Modification log" tab/link, which actually takes you to the log "module", but still looks like part of the patron profile. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 101

[Bug 21641] New: Software error when checking out an item with a charge associated with it
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '22

11 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21641 Bug ID: 21641 Summary: Software error when checking out an item with a charge associated with it Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When you try to check out an item with a charge associated with it the following error is thrown as the C4::Circulation->AddIssuingCharge() is executed: Undefined subroutine &C4::Circulation::getnextacctno called at /home/vagrant/kohaclone/C4/Circulation.pm line 3194 The getnextacctno function is in C4::Accounts. This module is in a use pragma at the top of C4/Circulation.pm -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 24980] New: Date formatting from JS - use timezone only with dates with offset
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '22

11 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24980 Bug ID: 24980 Summary: Date formatting from JS - use timezone only with dates with offset 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: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org Depends on: 24455 Blocks: 20936 Bug 24455 uses timezone to format any date that comes.. even dates like '2020-04-04' that specifies no offset. That date gets translated to '2020-04-04T00:00:00Z', and if you've got a timezone with -NN:NN if you ask for the date, you may get '2020-04-03' which is wrong. This bug will try to fix that. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20936 [Bug 20936] Holds History for patrons in OPAC https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24455 [Bug 24455] Date formatting from JS -- You are receiving this mail because: You are watching all bug changes.

1 42

[Bug 24455] New: date formatting from JS
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '22

11 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24455 Bug ID: 24455 Summary: date formatting from JS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: agustinmoyano(a)theke.io Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com API calls in OPAC brings raw JSON. We need a way to format data into the configured date from JS. -- You are receiving this mail because: You are watching all bug changes.

1 80

[Bug 23222] New: Fix DISABLE/ENABLE plugin label in plugins home
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '22

11 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23222 Bug ID: 23222 Summary: Fix DISABLE/ENABLE plugin label in plugins home Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Fix bug introduced in bug 21073 When you install a plugin, it shows as disables, even though it's enabled in database. Before 21073 that flag was called "enabled", after that bug it is called "is_enabled", but tt was never updated. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 24650] New: API returned timestamps are incompatible with existing helpers
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24650 Bug ID: 24650 Summary: API returned timestamps are incompatible with existing helpers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org API endpoints that return system maintained timestamps (specified as datetime in the DB schema and specified as 'date-time' in the endpoint definition) return the timestamps as a form of RFC3339 timestamps. For example, from the GET /patrons/{patron_id} response: "last_seen": "2020-02-13T08:47:29+00:00" This is good as it's in a standard form. However, all the existing handlers in koha-tmpl/intranet-tmpl/prog/en/includes/calendar.inc that are used to transform a received timestamp into the instance's defined format are expecting timestamps in the format: (see DateTime_from_syspref) [datestring] [hours:minutes] Thereby making it impossible to display a returned timestamp to the user in their chosen format. We either need to create additional helpers or modify the API returning of ISO formatted timestamps to something the helpers can cope with. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 24190] New: Add additional Acquisition logging
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24190 Bug ID: 24190 Summary: Add additional Acquisition logging Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org A start was made on adding logging for Acquisitions in bug 23971. This bug will extend this as detailed below (note, some of the information detailed here will be derived via reporting and not explicitly logged): 1. Order line cancellations Details including who made the cancellation and when the cancellation was made 2. Order line creations Details including who created the order line, when it was created, the fund, and amount 3. Invoice adjustment additions Details including who added the adjustment, when it was added, the fund, and amount 4. Invoice adjustment amendments Details including who amended the adjustment, when it was amended, the fund, and amount 5. Invoice adjustment deletions Details including who deleted the adjustment, when it was deleted, the fund, and amount 6. Order line receipts against an invoice Details including who received the order line, when it was received, the fund, and amount 7. Budget Adjustments This would show amounts added or removed from a budget (excluding spent), who, when, and amount (In Koha the actual amount is edited rather than typing in the amount to change) 8. Fund adjustments This is essentially a bank statement. It would show additions and subtractions to a fund (excluding spent), who, when, amount, previous total, new total 9. Order release date (1) This would show individual order lines from an EDI message, when they were sent, who sent it, fund, and amount 10. Order release date (2) This would show individual order lines from a basket, when it was closed, who closed it, fund, and amount -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 85

[Bug 24083] New: Koha should support "seen" vs "unseen" renewals
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24083 Bug ID: 24083 Summary: Koha should support "seen" vs "unseen" renewals 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: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When carrying out a renewal transaction Koha should check for both the maximum number of renewals allowed and also the number of unseen renewals. If it finds a value equal to or greater than the number of renewals already carried out against that loan, it prevents the renewal. The purpose of this is to prevent borrowers from continually renewing a book when they have, in fact, lost or misplaced it! When a renewal takes place via a method that doesn't require visible sight or possession of the item (e.g. OPAC, automatic renewal) then the number of unseen renewals for that item should be incremented. SIP2 renewals can be considered seen since they will require the physical item to be scanned. The number of allowed unseen renewals before a renewal is denied should be specifiable in the circulation rules. If a renewal is denied due to the unseen maximum having been reached, the flow should be the same as when a renewal limit has been reached, though with appropriate messages displayed to the user. It should be possible to override the denial in the same was as when a renewal limit is reached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 186

[Bug 23971] New: Add logging for basket relation actions
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23971 Bug ID: 23971 Summary: Add logging for basket relation actions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Acquisitions currently creates no action_logs. Some of our customers are requesting the addition of logs. The first stage of this work is to add the following logging: 1. Who created a basket and when Basket number, Basket name, Creation date, Vendor name, Creator name 2. Who edited a basket and when Basket number, Basket name, Edited date, Vendor name, Editor name 3. Who approved a basket and when Basket number, Basket name, Approval date, Vendor name, Who approved 4. Who closed a basket and when Basket number, Basket name, Closed date, Vendor name, Who closed (all should include EDI order information) This bug is related to Bug 13325, which requests logging of fund related actions -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 187

[Bug 22244] New: Typo in Mana Knowledge Base message
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22244 Bug ID: 22244 Summary: Typo in Mana Knowledge Base message 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: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- There is a typo in the message "You haven't decided if you want to activate Mana Knowlede Base, please let us know by clicking" The word "Knowledge" is misspelt -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11