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

[Bug 31078] New: Lost status different to 1 don't show with description in bundle detail view
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '22

08 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31078 Bug ID: 31078 Summary: Lost status different to 1 don't show with description in bundle detail view Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: trivial 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 Depends on: 28854 When a return claim for a bundle item is resolved into another status than "not lost", the lost status description will only show as the number on the bundle detail view. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28854 [Bug 28854] Add ability to create bundles of items -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 31079] New: Entering an empty line on checking of an item bundle, gives "Unexpected:" error
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '22

08 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31079 Bug ID: 31079 Summary: Entering an empty line on checking of an item bundle, gives "Unexpected:" error Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement 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 Depends on: 28854 When returning a checked out item bundle item, if you enter an additional new line in the field, you get an "Unexpected: " error. This could be a little confusing. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28854 [Bug 28854] Add ability to create bundles of items -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 28465] New: Staff Account Restrictions
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28465 Bug ID: 28465 Summary: Staff Account Restrictions Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: christofer.zorn(a)ajaxlibrary.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Hello All! One of our staff members had a mental lapse and deleted her own STAFF account the other day. Apparently Koha tried to stop her by preventing the deletion of either the account she was logged into, or by preventing her from deleting an account with a STAFF designation, but she was determined. She changed the account type from STAFF to COMPUSE, then the system didn’t stop her from deleting it. I'm proposing that if a staff member is not able to change another staff member's username, then they shouldn't be able to change the patron type of that account either. This would prevent a staff member from unintentionally (or otherwise) deleting a number of staff accounts. Thank you! Christofer -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 29032] New: ILL route unusable (slow)
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29032 Bug ID: 29032 Summary: ILL route unusable (slow) Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com With only 20 ill requests, for the same backend, the page takes lots of seconds to load. Steps to reproduce: 1. Add 23 requests with your favourite ILL backend 2. Hit the ILL requests page => FAIL: Notice it takes ages to load -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 31889] New: Restore MARC field order when embedding items
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31889 Bug ID: 31889 Summary: Restore MARC field order when embedding items 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org I would like to see 942 952 999 instead of 942 999 952. Tiny fix. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 31592] New: Fix ILL API following new date_due property
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '22

07 Nov '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31592 Bug ID: 31592 Summary: Fix ILL API following new date_due property Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Bug 24239 has broken the ILL /illrequests API endpoint. The bug added a date_due property to ILL requests, but the API schema was not updated accordingly, so requests to it now result in: {"message":"Properties not allowed: due_date.","path":"\/body\/0"} -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[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