January 2022 - Koha-bugs - lists.koha-community.org

[Bug 23628] New: Restrict Renewal when renewal period is not extending due date
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '22

22 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23628 Bug ID: 23628 Summary: Restrict Renewal when renewal period is not extending due date Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: mahsandu(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org When "OverduesBlockRenewing" enabled and Item's (due date + Renewal Period) is less than the current date: 1. Renewal button showing 2. After renewal it is setting due date as per "RenewalPeriodBase". 3. But new due date is in past. How to restrict user from renewal if this situation happened. It is creating misleading information. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29857] New: We must stringify our exceptions correctly
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '22

21 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29857 Bug ID: 29857 Summary: We must stringify our exceptions correctly Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: In Discussion Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 21022 We must have a generic full_message method in the Koha::Exceptions base class to display all the info we have about the exception. The current state is bad as we are displaying the "description" of the exception but it does not contain useful information. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21022 [Bug 21022] Exceptions should skip stringifying if message manually passed -- You are receiving this mail because: You are watching all bug changes.

1 71

[Bug 24254] New: Add Koha::Biblio get_visible_items method
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '22

21 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24254 Bug ID: 24254 Summary: Add Koha::Biblio get_visible_items method 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice to be able to fetch items excluding opac hidden items in one DB call rather than having to loop through items and compare to the rules for each. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 99

[Bug 23302] New: Allow faster access to Card and MARC view in Z3950 search results
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '22

21 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23302 Bug ID: 23302 Summary: Allow faster access to Card and MARC view in Z3950 search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In older versions it was possible to click Card view or MARC view directly. Now we must click twice (open menu first). When comparing different records, our users click Card or MARC repeatedly and would love to need only one click. What are our options to achieve that? ;) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 58

[Bug 23376] New: Cleanup order receive page
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '22

21 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23376 Bug ID: 23376 Summary: Cleanup order receive page 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 49

[Bug 29877] New: MaxReserves should be enforced consistently between staff interface and API
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '22

20 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29877 Bug ID: 29877 Summary: MaxReserves should be enforced consistently between staff interface and API Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major 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 To test: 1 - set maxreserves to 1 2 - set all/all circ rule to unlimited holds allowed total, holds allowed daily, and holds per record 3 - confirm you can place 1 hold for a patron via staff interface, but the second is blocked 4 - confirm you can place 1 for a patron via API, but the second is blocked 5 - set maxreserves to 0 6 - confirm you can place any number of holds for the patron via the staff interface 7 - confirm you can place 0 holds for your patron via the API 8 - set maxreserves to blank 9 - confirm you can place any number of holds for the patron 10 - confirm you can place 0 holds for your patron via the API We should make the API treat zero and blank as un-set, as the staff interface does. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 29754] New: Patron fines counted twice for SIP when NoIssuesChargeGuarantorsWithGuarantees is enabled
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '22

20 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29754 Bug ID: 29754 Summary: Patron fines counted twice for SIP when NoIssuesChargeGuarantorsWithGuarantees is enabled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The check for fines amount when using this pref fetches the patrons fines, then adds the total fines with guarantors, including this borrowers fines. This means the patrons own fines are doubled -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 26269] New: "Download file of displayed overdues" in Circulation->Overdues produces .csv with fewer results than the displayed list under certain circumstances
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '22

20 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26269 Bug ID: 26269 Summary: "Download file of displayed overdues" in Circulation->Overdues produces .csv with fewer results than the displayed list under certain circumstances 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: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org in Circulation->Overdues, when requesting the overdues for: - a FUTURE DATE (Date Due TO is > today ) AND - Show any items currently checked out IS checked, we get a list with several of results, as expected. However, when we click on the "Download file of displayed overdues", the overdue.pl script produces a .csv file with FEWER results and contains ONLY results that have "Date due TO < today". This was first discovered in our previous production Koha version (18.11.04), but is also valid in our current 18.11.11 version AND current master. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 29220] New: Minor fixes and improved code readability in circulation.pl
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '22

20 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29220 Bug ID: 29220 Summary: Minor fixes and improved code readability in circulation.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com While debugging another issue I found myself severely confused by some parts of the code in circulation.pl. By reviewing some earlier commits I worked out what is most likely the intent of the code and refactored it to clearer communicate that intent. The culprit of my confusion was this: https://github.com/Koha-Community/Koha/commit/1a8ca21875f86f25c72baf38e29d2… While the previous version was straight forward, this change is confusing since trying to do at least two things at once. What we want to do as far as I understand is to check for some serious errors (in this case UNKNOWN_BARCODE, but theoretically could be others as well) and allow forced onsite checkouts for all errors except for those ones. Since the display of all non blocking errors are hidden in the staff client for forced onsite checkouts, for consistency, these errors should also be hidden if some blocking error occurs. The alternative behavior would be very confusing. Now, only by chance, UNKNOWN_BARCODE is the first error in CanBookBeIssued to be checked for and retursn immediately after, so no other errors are ever registered in that case. But this could change in the future, and would cause a behavior where all errors are shown if a blocking error occur, but no errors are shown if not (for forced on site checkouts). I refactored this part to fix this issue and more clearly communicate the intended behavior. I also discovered some minor bugs introduced in various commits: https://github.com/Koha-Community/Koha/commit/2e72eb888016f60ce15958ecb37e0… "delete $question->{'DEBT'} if ($debt_confirmed);" is accidentally moved inside an if condition, when it should really always be performed as far as I can tell. https://github.com/Koha-Community/Koha/commit/7a7a0a2474c958e85b96db55bba04… Here an explicit check for DEBT_GUARANTORS is added, as a blocking error (an error that will not be ignored for on site checkouts with OnSiteCheckoutsForce enabled. That seems inconsistent with the settings description "Enable/Disable the on-site for all cases (Even if a user is debarred, etc." and the fact that all other errors returned by CanBookBeIssued UNKNOWN_BARCODE are ignored. This includes DEBT_GUARANTEES, DEBT, RESTRICTED etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 29886] New: Add Koha::Suggestions->search_limited
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '22

20 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29886 Bug ID: 29886 Summary: Add Koha::Suggestions->search_limited 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org SearchSuggestion does filtering on IndependentBranches, etc. We need to implement Koha::Suggestions->search_limited that does that as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28