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

[Bug 31181] New: Merge function does not include local copy images
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31181 Bug ID: 31181 Summary: Merge function does not include local copy images Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It seems that merge-from item local cover images are not merged to the merge-to entry. Is thie intentional or is it a bug? If intentinal there should be a warning to the user before the merge is performed, so that they may save the current images and re-locad them once the merging is complete. Are the images left in limbo, or are they deleted from the db once the merge is complete? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 26820] New: "Important" flag enforced only at subfield level
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26820 Bug ID: 26820 Summary: "Important" flag enforced only at subfield level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: - edit your framework so the 001 is set to Important at the tag level but not at the subfield level - create a new record in that framework, note that the 001 is not marked Important - edit framework, set it to Important on the @ subfield in the 001 - reload new record, see the 001 is now marked Important We're not doing anything with Important at the tag level, so let's not ask for it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 14367] History for MARC records. Roll back changes on a timeline or per field.
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14367 Miranda Nero <mnero(a)oslri.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mnero(a)oslri.net -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14367] History for MARC records. Roll back changes on a timeline or per field.
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14367 Heather <flyingendpaper(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |flyingendpaper(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38017] New: Add an on/off switch for the bookings feature
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38017 Bug ID: 38017 Summary: Add an on/off switch for the bookings feature Change sponsored?: --- Product: Koha Version: Main 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: 29002 Currently there is no way to turn off the bookings feature. This means that the bookable option on item details is always visible as are the new circulation rule options. We'd like this to depend on a system preference that allowed to turn off the feature completely and remove those options from the GUI. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29002 [Bug 29002] Add ability to book items ahead of time -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 34924] New: Add ability to send 'final auto renewal notice'
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34924 Bug ID: 34924 Summary: Add ability to send 'final auto renewal notice' 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com See bugs 19014 and 31427 - users can end up receiving an auto renewal failure immediately after a success. 31427 updates to send this notice at the end of a circ period, but then the user doesn't know the book won't renew until it is nearly due We should have a way to mark that an issue has reached the end of the allowed renewals and warn the user that the item won't be renewed when it becomes due. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 50

[Bug 38111] New: Update manager option broken in Change selected suggestions section
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38111 Bug ID: 38111 Summary: Update manager option broken in Change selected suggestions section Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: heather(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 172502 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=172502&action=e… Screenshot of update manager option On the Suggestions management page, beneath the table there is a Change selected suggestions section. Within this section, the Update manager option is broken in 24.05. Users can click on Select manager to conduct a patron search, but the selected patron name is not retained and not applied to the selected suggestions when the Submit button is clicked. Instead, the Managed by column in the table is updated with the name of the logged in user when the Submit button is clicked. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 35017] New: If creating items when ordering, an alert should appear if the item type is not filled out
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35017 Bug ID: 35017 Summary: If creating items when ordering, an alert should appear if the item type is not filled out Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Step to reproduce 1. Create a basket 2. Choose to create items upon ordering 3. Use either a new file or a staged file 4. When adding records to the basket, the required fields seem to only be fund and price. Fill out the required fields. 5. Close the basket 6. Go to receive from that vendor, - add invoice number, then see a 500 error instead of being able to receive anything from that vendor. When a basket is created in Acquisitions with the "create items on ordering", but the item type is not filled in, a 500 error will appear when attempting to receive. Although the item type is not required, thus allowing a user to go through the whole process only to receive a 500 error when receiving. This error will appear regardless of what the user is receiving if an order within that vendor has an order without an item type. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 36483] New: Calling $object->to_api directly should be avoided
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36483 Bug ID: 36483 Summary: Calling $object->to_api directly should be avoided Change sponsored?: --- Product: Koha Version: master 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 Highlighted on bug 36482, calling $object->to_api directly on our API controllers makes several parameters ineffective. Notably, x-koha-embed. We should call instead: ```perl $c->objects->to_api( $object ) ``` A follow-up bug replacing all existing calls should've been filled but we somehow missed it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 38151] New: Cumulative restriction does not apply when return in batch
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38151 Bug ID: 38151 Summary: Cumulative restriction does not apply when return in batch Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hagud(a)orex.es QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Koha has the preference CumulativeRestrictionPeriodst that allow to sum restriction for each item overdued This is not working when returning items at once from user's detail page, it only applies first suspension. When returning from circulation module one by one it works fine. test plan: a) Configure circulation rule with 1 days of suspension for earch overdue day b) issue two items to any user c) 2 days after due date return both items at one from moremmebers, it will be suspended 2 days instead 2 + 2 d) issue two items again to any other user c) 2 days after the due date, go to circulation module -- return, d) return one by one... e) the user is restrictd 2 + 2 I have checked from 23.05 and 23.11 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3