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

[Bug 36571] New: Item search is broken when using 'is not' for searching
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '24

11 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36571 Bug ID: 36571 Summary: Item search is broken when using 'is not' for searching 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: 1. Go to item search. 2. Select multiple parameters and choose 'is not' 3. The search does not return items correctly. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 36519] New: There should be a way to dismiss the suggestions in SQ report editor
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '24

11 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36519 Bug ID: 36519 Summary: There should be a way to dismiss the suggestions in SQ report editor 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When writing reports it can be helpful to insert newlines in order to make the report more readable, e.g.: SELECT title, author FROM biblo WHERE author LIKE CONCAT('%',<<Author partial name>>,'%') Trying to do so with suggestions requires a mouse click to close the suggestions window. Type 'SELECT' and press enter - it just keeps suggesting 'SELECT' insert a space and it begins suggesting new things and won't clear until you click with the mouse I would expect something like ESC to clear the suggestions window -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 31074] New: Plugin metadata is kept in cache after uninstalling a plugin
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '24

11 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31074 Bug ID: 31074 Summary: Plugin metadata is kept in cache after uninstalling a plugin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org == test plan == 1. Install a plugin, like the kitchen sink https://github.com/bywatersolutions/dev-koha-plugin-kitchen-sink/releases 2. Modify the .kpz and in KitchenSink.pm, change MINIMUN_VERSION 3. Uninstall the plugin 4. Install the new version 5. The Minimum Koha version column still lists the old version 6. restart services 7. The Minimum Koha version column is correct now -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 58

[Bug 26177] New: The 'set library' functionality should be changed to 'session settings' or similar
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '24

11 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26177 Bug ID: 26177 Summary: The 'set library' functionality should be changed to 'session settings' or similar 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 The set library controller and template will soon allow the setting of other session level information like 'desk' and 'cash register'.. as such we should rename and clean up the controller and template to reflect their new functionality. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 34491] New: Add select2 to fund selection in adjustments (invoice)
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '24

11 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34491 Bug ID: 34491 Summary: Add select2 to fund selection in adjustments (invoice) 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: michaela.sieber(a)kit.edu QA Contact: testopia(a)bugs.koha-community.org When you have a lot of funds, would be useful to have autocompletion in funds combobox in the invoice adjustments section Test plan : 1. Go to acquisition modul 2. Create an activ and an inactiv budget with at least one fund 3. Search for Vendor 4. Button receive shipment and create invoice 5. Click finish receiving (we don't need an order line for this test) 6. Click +Add an adjustment There is no autocompletion in 'Fund' combobox 7. Apply Patch 8. Search for your invoice 9. Click +Add an adjustment 10. Check you see autocompletion in 'Fund' combobox 11. Click on 'Show inactive' 12. Check you see inactiv funds in combobox 13. Update adjustments 14. Change the fund in the existing adjustment line using the autocompletion -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 36573] New: Fund should be a mandatory field for invoice adjustments
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '24

11 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36573 Bug ID: 36573 Summary: Fund should be a mandatory field for invoice adjustments Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: philip.orr(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org Currently you can enter an invoice adjustment without selecting a fund. In this case the adjustment amount will be shown in that specific invoice but will not be respected in the funds table on the acquisitions start page. To replicate: Add an adjustment to an invoice. Do not select a fund when adding the adjustment. Look at the acquisitions start page - the adjustment amount is not included in the 'Spent' column. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 34713] New: Standardize plugin hooks
by bugzilla-daemon＠bugs.koha-community.org 11 Apr '24

11 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34713 Bug ID: 34713 Summary: Standardize plugin hooks Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: In Discussion Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart+koha(a)gmail.com, katrin.fischer(a)bsz-bw.de, m.de.rooy(a)rijksmuseum.nl, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, oleonard(a)myacpl.org, tomascohen(a)gmail.com We should standardize the way plugin hooks are implemented and behave. Looking at: https://wiki.koha-community.org/wiki/Koha_Plugin_Hooks https://github.com/bywatersolutions/dev-koha-plugin-kitchen-sink Some hooks are called like: Koha::Plugins->new()->GetPlugins( { method => 'background_tasks', } ); and then the respective method invoked Others are just called like: Koha::Plugins->call('patron_barcode_transform', \$patron_id ); Some hooks return stuff (e.g. opac_detail_xslt_variables), others expect the param to be a ref and change in place without returning anything (e.g. patron_barcode_transform) --- Discussion: We already have hooks that behave like actions, and others that behave like filters. Wordpress put's it this way: - an action interrupts the code flow to do something, and then returns back to the normal flow without modifying anything; - a filter is used to modify something in a specific way so that the modification is then used by code later on. My proposal is: - Make it clear that a hook is either an action or a filter, either by name or by the way it's called - All actions should implement the same (example) Plugins->call('action_name', $args) signature - All filters should implement the same (example) Plugins->call('filter_name', $args) signature and return $args -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 36570] New: OAI-PMH - Hide items non-public notes
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '24

10 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36570 Bug ID: 36570 Summary: OAI-PMH - Hide items non-public notes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org After enabling the expose of items (`include_items: 1` on `OAI-PMH:ConfFile`) the info of 952$x Non-public note (items.itemnotes_nonpublic) is shown, potentially exposing sensitive information. Not sure how a solution to this issue may interact with OpacHiddenItems. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 5807] Add collection code to circulation rules
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '24

10 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5807 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au --- Comment #5 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Katrin Fischer from comment #1) > Itemtypes can now be grouped to make things a little easier for end users. > Overall I am not sure if using a 4th dimension would make circulation rules > still managemable: library - patron category - itemtype - collection Agreed. They're already borderline unmanageable. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 9762] Log circulation overrides
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '24

10 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9762 Katie Bliss <kebliss(a)dmpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kebliss(a)dmpl.org -- You are receiving this mail because: You are watching all bug changes.

1 0