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

[Bug 24009] New: Koha::Account->outstanding_debits should support inline filtering
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24009 Bug ID: 24009 Summary: Koha::Account->outstanding_debits should support inline filtering 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We have a number of places where we want to get a specific list of outstanding debits for comparison.. at the moment one would have to construct a search directly by inspecting system preferences at the controller level. By addins a filter option to oustanding_debits we can move that back to the object level without having to add additional methods. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 30654] New: Even with RabbitMQ enabled, we should poll the database for jobs at worker startup
by bugzilla-daemon＠bugs.koha-community.org 01 Aug '24

01 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30654 Bug ID: 30654 Summary: Even with RabbitMQ enabled, we should poll the database for jobs at worker startup 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 27344 Our worker currently starts up and immediately tries to listen for jobs being passed via STOMP. However, if rabbitMQ wasn't running when the tasks were enqueue, then the worker will never know about them. We should work through the outstanding queue before listening for new jobs. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27344 [Bug 27344] Implement Elastic's update_index_background using Koha::BackgroundJob -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 35299] New: Allow for items with specific not for loan values to appear in the holds queue
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '24

31 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35299 Bug ID: 35299 Summary: Allow for items with specific not for loan values to appear in the holds queue 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: clemens.tubach(a)kit.edu, gmcharlt(a)gmail.com, michaela.sieber(a)kit.edu We’d like to be able to specify a list of not for loan values that will be considered eligible to fill holds and appear in the holds queue and ideally the pending holds list as well. These would usually be negative not for loan values, that can be placed on hold. It should be possible to still exempt some status, like -1 = on order. Use Case: In libraries with closed stacks there are often items that are not for loan, but can be requested for use in a reading room. Staff will then get the items and fill the holds, but they won't be checked out on self checks etc. An on-site checkout might be forced. (see Library of Congress: https://ask.loc.gov/law/faq/300644) In order for this process to work the library needs the information about the requested items in order to be able to pull the items in the closed stacks. We have tested a change in Holdsqueue.pm that works, but should be made properly configurable: https://git.koha-community.org/Koha-community/Koha/src/branch/master/C4/Hol… Change: $items_query .= " WHERE items.notforloan = 0 To: $items_query .= " WHERE items.notforloan in (-2, -3, 09) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 36717] New: Merge "Patrons (custom slip)" and "Patrons (custom message)" in Notices
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36717 Bug ID: 36717 Summary: Merge "Patrons (custom slip)" and "Patrons (custom message)" in Notices Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org With the introduction of custom email messages in Bug 29393, we discussed (https://chat.koha-community.org/koha-community/pl/ixoy58im47dhpr4gmwtn9sdbjw) the opportunity to merge the "Patrons (custom slip)" notice type introduced in Bug 32986 and the new "Patrons (custom message)" notice type. The "custom slips" would be notices with the print message transport type, and the "custom messages" (email messages) would be notices with the email message transport type. To get there: 1. Go to Tools > Notices and slips 2. Click New notice --> Notice there is a category "Patrons (custom slip)" and (after bug 29393) "Patrons (custom message)" Create and use a custom slip 3. Click "Patrons (custom slip)" 4. Enter a code and a name (e.g. TESTSLIP, Test slip) 5. Click the "Print" tab 6. Enter content in the "Message subject" and "Message body" fields 7. Click "Save" 8. Go to a patron's account 9. Click "Print" --> There should be an option to "Print test slip" (or whatever name you gave it) Create and use a custom message 10. Go back to Tools > Notices and slips > New notice 11. Click "Patrons (custom message)" 12. Enter a code and a name (e.g. TESTMESSAGE, Test message) 13. Click the "Email" tab 14. Enter content in the "Message subject" and "Message body" fields 15. Click "Save" 16. Go to a patron's account 17. Make sure the patron has an email address 18. Click "Add message" 19. In "Add message for" choose Email --> In "Patron notice" there should be "Test message" (or whatever name you gave it) The proposition was to merge the two notice types and only show the ones with the "Print" message transport type filled in the "Print" menu, and only show the ones with the "Email" message transport type filled in the "Add message" menu. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 35189] New: Itemtypes SVG icons should be limited in height/width
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35189 Bug ID: 35189 Summary: Itemtypes SVG icons should be limited in height/width Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 158067 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=158067&action=e… Screenshot Steps to reproduce the issue: 1. On Staff interface, on Administration > Item types, modify any item 2. Choose an SVG image as a remote image for an Item type, for eg https://raw.githubusercontent.com/FortAwesome/Font-Awesome/afecf2af5d897b76… Save changes. When listed on itemtypes.pl the icon is not too big, but if you edit again the itemtype (using above SVG, more than 1200px width). This also impact at some degree on Advanced search (staff and OPAC, search.pl, opac-search.pl). -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 35155] New: MARCOverlayRules syspref not in manual
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35155 Bug ID: 35155 Summary: MARCOverlayRules syspref not in manual Change sponsored?: --- Product: Koha Version: unspecified Hardware: All URL: https://gitlab.com/gnucifer/koha-manual/-/commit/593c5 da008dbc4b074cac9dee167cce9a6dfc250#c5e2c75dc923f21c5b 95185b2f350df00fec661f OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 14957 MARCOverlayRules system pref and functionality introduced in 21.11 never made it into Koha manual. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 [Bug 14957] Write protecting MARC fields based on source of import -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 25610] New: Inconsistent display of 856$3 in OPAC between brief result and full record
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25610 Bug ID: 25610 Summary: Inconsistent display of 856$3 in OPAC between brief result and full record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently, if a record has an 856$3, this will show in the brief results and not in the full results. It should be consistent between the two views. And what is the opinion that the $3 should show or should not? For decisions like these, it would be nice for the library to decide what is displayed and allow for changes to be made through the staff client vs XSLT stylesheets. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 36194] New: CSRF - svc
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '24

30 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36194 Bug ID: 36194 Summary: CSRF - svc Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This bug is for tracking follow-ups missed in the initial review. Please see the "svc" section on the framapad here: https://annuel.framapad.org/p/koha_34478_remaining Additional entries can be added there, and should be crossed out when completed Patches should be attached here This bug can be closed when that section of the pad is empty see bug 36084 commits for new method using fetch/api-client.js is retrieved (and adjusted) from the Vue work wiki/coding guideline to follow -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 25884] New: Automatic item modifications by age needs title and description fields
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '24

29 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25884 Bug ID: 25884 Summary: Automatic item modifications by age needs title and description fields Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org We need to be able to label and describe these rules outside of the settings we set. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 35726] New: Add ability to edit automatic item modification by age rules individually
by bugzilla-daemon＠bugs.koha-community.org 29 Jul '24

29 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35726 Bug ID: 35726 Summary: Add ability to edit automatic item modification by age rules individually Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When there are several rules, it would be nice if it were possible to edit individual rules. Right now, in order to edit one rule, all rules are opened for editing. This could be done by adding an edit button at the end of the row in the table that lists the rules. As an extension, the rules table should be sortable. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1