May 2023 - Koha-bugs - lists.koha-community.org

[Bug 19166] New: Add the ability to add adjustments to an invoice
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19166 Bug ID: 19166 Summary: Add the ability to add adjustments to an invoice Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The goal of this enhancement is to allow libraries to make adjustments to invoices based on feedback form a vendor (credit for returned books, damaged books, or fees for extra charges etc.) -- You are receiving this mail because: You are watching all bug changes.

1 158

[Bug 20824] New: Display of cancelled Orders show up in Acquisitions
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20824 Bug ID: 20824 Summary: Display of cancelled Orders show up in Acquisitions Change sponsored?: --- Product: Koha Version: 17.11 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 Currently, any orders that have been cancelled will show up in Acquisitions (basket.pl). It would be nice from a display side, to have this view (cancelled orders ) be collapsed so if needed, they are still viewable, but generally they do not appear on this screen. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 23989] New: Enable SSO options for SelfCheck modules for Koha
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23989 Bug ID: 23989 Summary: Enable SSO options for SelfCheck modules for Koha Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently the self check module allow users to sign in via cardnumber, or userid/password. The sign in form should be extended to allow SSO options (LDAP/Shibboleth/OAuth/etc.) on this login form. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 30444] New: Enable Shibboleth option for SelfCheck modules for Koha
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30444 Bug ID: 30444 Summary: Enable Shibboleth option for SelfCheck modules for Koha Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Add 'Shibboleth' to the SelfCheckoutByLogin system preference, so users can sign into the self-checkout page via Shibboleth. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[Bug 17723] New: Using MySQL on external server - lack of documentation giving example
by bugzilla-daemon＠bugs.koha-community.org 30 Jun '23

30 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17723 Bug ID: 17723 Summary: Using MySQL on external server - lack of documentation giving example Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Project website Assignee: wizzyrea(a)gmail.com Reporter: fooquency(a)gmail.com I am trying to create a Koha instance using MySQL on a remote server. https://wiki.koha-community.org/wiki/Debian#Create_a_Koha_instance states: "create a new file in its place containing the connection information for the server, in the form of a my.cnf file." but no example is given. I would assume this somehow allows specification of all of hostname, username and password, but it is entirely unclear currently how to do this. Could someone kindly add an example or give more details of what format exactly "the connection information" should be in? http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html has no mention of a password configuration for instance. -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 31031] New: MarkLostItemsAsReturned does not work with batch item modification
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '23

29 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31031 Bug ID: 31031 Summary: MarkLostItemsAsReturned does not work with batch item modification Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If you choose the "from the batch item modification tool" in the MarkLostItemsAsReturned preference, it does not work. Status is changed as usual, but it does not check the item(s) in. This means for now, staff have to do this manually, one item at a time! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 26495] New: Impossible to save Budget Plans
by bugzilla-daemon＠bugs.koha-community.org 29 Jun '23

29 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26495 Bug ID: 26495 Summary: Impossible to save Budget Plans Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org In master, it's impossible to save Budget Plans as there is no save button. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31844] New: Clarify cataloging permissions
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '23

28 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31844 Bug ID: 31844 Summary: Clarify cataloging permissions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client 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 Bug 31162 migrates cataloging related tools into a new clarified cataloging module home page. We should migrate the various permissions related to these functions into the editcatalog permissions. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 31611] New: More visibly highlight records that cannot be batch deleted/modified
by bugzilla-daemon＠bugs.koha-community.org 28 Jun '23

28 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31611 Bug ID: 31611 Summary: More visibly highlight records that cannot be batch deleted/modified 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: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Currently, on the 'Batch item deletion', 'Batch item modification', and 'Batch record deletion' tools if a record cannot be modified/deleted it is displayed in the table of records with a disabled (greyed-out) checkbox. To replicate: 1. Check out an item 2. Go to Tools > Batch item deletion 3. Enter the barcode of the checked-out item and submit 4. Observe the item is displayed in a table with a disabled checkbox 5. Select 'Delete selected items' 6. Notice the checked-out item is not deleted When libraries are modifying/deleting large numbers of records it's easy for them to miss the disabled checkboxes when scrolling through the table. The consequence of this is then wondering why some records have not been modified/deleted. It would be useful to more clearly highlight records that cannot be modified/deleted for these tools. Proposed solution: - Replace the disabled checkbox with a red cross (like those displayed beside items on hold pages when you're not allowed to place item-level holds). - Highlight the entire row for the record that cannot be modified/deleted with a yellow background. - In the 'Batch item deletion' and 'Batch item modification' remove the 'Clear on loan' link - introduced in bug 10599 - as removing the disabled checkboxes would make this redundant. --- I could not see disabled checkboxes in use in the 'Batch patron deletion and anonymisation', 'Batch patron modification', 'Batch extend due dates', or 'Batch record modification. However, I may have missed it so please do let me know if it is present there so I can apply my proposed solution to those pages to for consistency :) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 17311] New: koha-common service should be restarted on upgrade
by bugzilla-daemon＠bugs.koha-community.org 27 Jun '23

27 Jun '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17311 Bug ID: 17311 Summary: koha-common service should be restarted on upgrade Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net The upgrade process should restart the koha-common service. This is needed so Plack processes are restarted too and Koha version is reloaded (otherwise end users keep getting upgrade messages on the UI. Any other patched file will be reloaded (apache, zebra, etc). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19