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

[Bug 33192] New: We should rename 'AutoEmailPrimaryAddress' to 'EmailFieldPrimary' for clarification
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '24

28 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33192 Bug ID: 33192 Summary: We should rename 'AutoEmailPrimaryAddress' to 'EmailFieldPrimary' for clarification Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The AutoEmailPrimaryAddress preference no longer only affects AutoEmailNewUser (formerly known as AutoEmailOpacUser). As such I feel it should be clarified and renamed to EmailFieldPrimary to show it is actually being used for the majority of notices now. I chose EmailField* to sit it next to the new preference I attempt to introduce in bug 29046. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 34922] New: Populate amount with replacementprice/price when creating an invoice
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '24

28 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34922 Bug ID: 34922 Summary: Populate amount with replacementprice/price when creating an invoice Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some librarians would find it handy if the "amount" field was populated with the replacementprice/price after adding the barcode to a manual invoice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 30069] New: Add edifact_messages to cleanup_database.pl
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '24

28 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30069 Bug ID: 30069 Summary: Add edifact_messages to cleanup_database.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz We should add the ability to clean up old edifact messages with cleanup database. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 36015] New: New features in batch modification template management
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '24

28 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36015 Bug ID: 36015 Summary: New features in batch modification template management Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: infoscienceaddict(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl As we use batch record modification quite often, we apply many templates regularly. The problem is that their number has grown significantly. It would be good to arrange them in folders so that we can separate the ones about authorities from those about bibliographic records. Also, some options to sort them (i.e. alphabetically, by description, etc.) would be great. Last but not least, it would be great if we could rename an existing template could become handy. At first, we didn't use explanatory names for each template, so now it's hard to find a template in their whole batch. I hope someone else out there thinks these would be useful! Thank you! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 35077] New: pinning perl Elasticsearch client version to "< 8.0"
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '24

28 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35077 Bug ID: 35077 Summary: pinning perl Elasticsearch client version to "< 8.0" Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: Linux Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: davewood(a)gmx.at if you install Koha on debian 12 (bookworm) you will end up with version 8 of the module https://metacpan.org/pod/Search::Elasticsearch at the moment of writing this bug report this module doesnt work with ES 7.0 (the latest ES version that I am aware works with Koha 23.05 changing the version requirement in https://github.com/Koha-Community/Koha/blob/master/cpanfile#L99) to ``` requires 'Search::Elasticsearch', '< 8.00'; ``` currently installs Search-Elasticsearch-7.717 which seems to work for me. current workaround for our system. run `cpanm Search::Elasticsearch~"< 8.00"` -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 30592] New: Move borrowers.secret to a new generic credentials table
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '24

27 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30592 Bug ID: 30592 Summary: Move borrowers.secret to a new generic credentials table 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org This generic credentials table should allow for storing other secrets, passwords, etc. too. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 21638] New: Allow reporting of holds cancelled by cancel_expired_holds.pl and ExpireReservesMaxPickUpDelay
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '24

26 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21638 Bug ID: 21638 Summary: Allow reporting of holds cancelled by cancel_expired_holds.pl and ExpireReservesMaxPickUpDelay Change sponsored?: --- Product: Koha Version: 18.05 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 When ExpireReservesMaxPickUpDelay is set to Allow, waiting holds are automatically cancelled by cancel_expired_holds.pl. But, generally, libraries still need to physically remove those items from their hold shelf and check them in to guarantee there are not pending holds or transfers to be triggered. A report to identify these items is imperfect and cannot definitively distinguish a hold cancelled by the cron from a hold cancelled by an employee. Bug 14134 established behavior that displays holds which *will* be cancelled by the next run of the cron on the "holds over" tab in Holds Awaiting Pickup, but doesn't allow staff to see which holds have already been cancelled. It'd be great if the cron could email a list of cancelled holds. Additionally, reporting would be improved by the introduction of a new value in old_reserves.found for items cancelled by the cron (maybe E for expired). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26317] New: Misleading choices from reports error when runtime parameter is named incorrectly
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '24

26 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26317 Bug ID: 26317 Summary: Misleading choices from reports error when runtime parameter is named incorrectly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: - create a new report from SQL - enter "SELECT <<whatever|whatever>>" and try to save - Get an error "Errors found when processing parameters for report: whatever: The authorized value category (whatever) you selected does not exist." - Error provides two options, "Save Anyway" or "Edit SQL" - Click Edit SQL, get taken to an empty report "Edit SQL" wants to take you back to the previously saved version of your report. But if you've ended up at this error from a brand new report that's never been saved, then the "Edit SQL" button is going to take you to a blank report, trashing whatever you've just written. If we can't retain that SQL through the error on an unsaved report, then we should remove the Edit SQL button when working with a report that hasn't been saved yet. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 28404] New: Improve calendar tool management
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '24

26 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28404 Bug ID: 28404 Summary: Improve calendar tool management Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org 1. It would be great if libraries could delete holidays from the calendar tool. Because they can’t be deleted by our library we end up with lots of old holidays in the table and sometimes incorrect entries. 2. Holidays display in date ascending order which means the oldest ones are listed first. When you have a long list of old holidays this means you have to do a lot of scrolling to get to the current year. It would be very useful if the holidays could sort in year descending order and within each year the dates would sort in date ascending order. This would put the most current dates at the top of the table for quicker viewing. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 21348] New: Add ability to export and import plugin data
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '24

26 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21348 Bug ID: 21348 Summary: Add ability to export and import plugin data 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We could possibly add a way to download a specific plugin's data from plugin_data in some arbitrary file format, and also add a facility to re-insert that data back into the plugin_data table. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3