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

[Bug 35121] New: Display libraries using the Authorized Value instead of number of libraries
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '23

21 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35121 Bug ID: 35121 Summary: Display libraries using the Authorized Value instead of number of libraries Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently, within Authorized Values, when a specific value has a library limitation, Koha just displays the number of libraries using this value. It would be helpful to instead display the libraries using this value. For example, if 2 libraries out of 5 libraries used the Collection Code: Graphic Novels, under the Library Limitation for this value, it would be nice if it listed out the names of the 2 libraries using the Graphic Novel Collection Code. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 31175] New: OPAC Logout should return you to where you were (unless that's a restricted page)
by bugzilla-daemon＠bugs.koha-community.org 21 Nov '23

21 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31175 Bug ID: 31175 Summary: OPAC Logout should return you to where you were (unless that's a restricted page) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The OPAC logout appears to always take you back to opac-main. To test 1) Perform a search 2) Go to the details of a search results 3) Logout 4) Note, you are no longer on the defail page for the record you had searched for. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 31630] New: Batch item deletion no longer shows which items were not removed
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31630 Bug ID: 31630 Summary: Batch item deletion no longer shows which items were not removed Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lnilsson(a)lewistonschools.net QA Contact: testopia(a)bugs.koha-community.org The only warning > given is an unclicked box and when deleting long lists it is hard to notice. > The follow up page use to have a notification stating some barcodes were not > deleted, please help. Thanks, LeeAnn Same problem I had with closed Bug 28353 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 12478] Elasticsearch support for Koha
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12478 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |35372 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35372 [Bug 35372] Support for empty AdvancedSearchTypes -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 33619] New: the "update sql" window isn't showing obsolete fields and their new names.
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33619 Bug ID: 33619 Summary: the "update sql" window isn't showing obsolete fields and their new names. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: marie-luce.laflamme(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org The “update sql” button of an obsolete report has stopped describing fields that need to be fixed. If your report still contains a biblioitems.marcxml field, Koha will warn with a “This report seems obsolete” message. Then, you can click on the “update sql” button to fix the report, and Koha will open up a popup window. Unfortunately, this window is no longer showing obsolete fields and their new names. Instead, there is only a loading cursor on display without any explanations. At this point, you aren't sure if you can click on the "update" button within the window, thinking it may be broken. But if you try, Koha will update the report correctly. Is there a way to bring back the previous version behaviour in this window? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 15977] New: Optional double screen message in Patron Info/Status
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15977 Bug ID: 15977 Summary: Optional double screen message in Patron Info/Status Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com This code in MsgType.pm: $resp .= maybe_add( FID_SCREEN_MSG, $patron->{branchcode}, $server ) if ( $server->{account}->{send_patron_home_library_in_af} ); produces two AFs if you enable that attribute in your config. Not sure if that should be the case and is conform protocol. Also: are we solving a problem here in the wrong place? It looks kind of inappropriate use.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 34680] New: Renewal due date -> different due times (HH:MM) depending on the input method
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34680 Bug ID: 34680 Summary: Renewal due date -> different due times (HH:MM) depending on the input method Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: irina.halminen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 155028 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=155028&action=e… Renewal due date When setting a renewal due date from the bottom of the circulation page (/cgi-bin/koha/circ/circulation.pl? -> Check out) and typing the due date by hand (not selecting it from the calendar) and pressing Enter, the system sets the due time (HH:MM) automatically, and it differs from the default. For example, our due time is set to be 23:59, but when I type in the renewal due date, it sets the due time to be 00:00. So if the due date is October 31st and the due time is 00:00, all the loans are overdue a minute after the midnight on the due date. Using the calendar and using the manual typing method should both end up in the same result (default HH:MM). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 34939] New: When manually entering dates in flatPickr the hour and minute get set to 00:00 not 23:59
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34939 Bug ID: 34939 Summary: When manually entering dates in flatPickr the hour and minute get set to 00:00 not 23:59 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org With flatPickr you can manually enter a date. If that date date allows for the input of hours and minutes and you do not manually specify those the default will be 00:00. When you use the flatPickr calendar to pick a date time and no do specify the hour/minute it will default to 23:59. This should be consistent. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 35367] New: Add option to link an ordered item to a suggestion after the order has been created
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35367 Bug ID: 35367 Summary: Add option to link an ordered item to a suggestion after the order has been created 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Sometimes library staff forget to add an order to a basket from a suggestion, even though the relevant suggestion exists and has been accepted. It would be great to have an option to link a suggestion to an order after it has been created. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 14293] Error in the calculation of the suspension of users per day
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '23

20 Nov '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14293 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david(a)davidnind.com --- Comment #49 from David Nind <david(a)davidnind.com> --- I've tested and signed off. But feel free to change back to "Needs signoff" if this isn't sufficient. (I'm always nervous about testing circulation and fine rules - "Here be dragons".) Testing notes using KTD: 1. Set the "All All" rule as follows: - Unit: change from Days to Hours - Suspension in days (day): change from blank to 2 - Max. suspension duration (day): left blank - Suspension charging interval: 1 2. Items checked out on 20 November 2023. 3. Results before the patch was applied (I set the due date for an item to 11/09/2023). When checked in, the message says: "[Patron name] is now debarred until 06/05/2055." 4. After the patch was applied, the message on check in says: "[Patron name] is now debarred until 12/10/2023." - Matches what was expected: difference between due date and checked in date = 10; x2 = 20 days = 12/10/2023 5. I then set "Suspension in days (day)" to 1. The message on check in says: "[Patron name] is now debarred until 11/30/2023." - Matches what was expected: difference between due date and checked in date = 10; x1 = 10 days = 11/30/2023 6. The tests pass: prove t/db_dependent/Circulation/maxsuspensiondays.t -- You are receiving this mail because: You are watching all bug changes.

1 0