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

[Bug 31981] New: Need to be able to more clearly distinguish between hold warning boxes
by bugzilla-daemon＠bugs.koha-community.org 28 May '24

28 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31981 Bug ID: 31981 Summary: Need to be able to more clearly distinguish between hold warning boxes Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 142657 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=142657&action=e… warning box for example two There are potentially two yellow warning boxes staff can see when checking out an item that is on hold and the two boxes are VERY difficult to distinguish between. It would be helpful to either change the wording, or change the color of one of them to help staff determine what action should be taken. For instance, place a hold on an item for Patron A, do not trigger the hold, and check the item out to Patron B. The message is: Please confirm checkout Item Toby goes bananas / (312824) has been on hold for Donna B (donnab) at Sparkly Unicorn Land since 10/25/2022 Cancel hold Yes, check out (Y) Don't check out and print slip (P) No, don't check out (N) Cancel checkout and place a hold for Jack Shepard (68) Then check the item in, confirm the hold, then check the item out to Patron B. The message is: Please confirm checkout Item Toby goes bananas / (312824) has been waiting for Donna B (donnab) at Sparkly Unicorn Land since 10/25/2022 Cancel hold Revert waiting status The first message is much more common - libraries typically see it when a patron has placed a hold on something, but another patron has taken it off the shelf to check out before staff were able to pull it for the other patron. The second message is much less common - this is when an item is on the hold pick up shelf and a patron other than who it was triggered for is trying to check it out. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 35954] New: Add --status to koha-plack
by bugzilla-daemon＠bugs.koha-community.org 28 May '24

28 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35954 Bug ID: 35954 Summary: Add --status to koha-plack 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz There is already a function called is_plack_running in koha-functions.sh. https://git.koha-community.org/Koha-community/Koha/src/branch/master/debian… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 36614] New: Reinstate Phone column in patron search
by bugzilla-daemon＠bugs.koha-community.org 28 May '24

28 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36614 Bug ID: 36614 Summary: Reinstate Phone column in patron search 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When performing a patron search (either through Patrons or Check out), there is no way to see the patron's phone number. This functionality was added in bug 17353, but the table has changed since then from table_borrowers to memberresultst. memberresultst doesn't have a phone number column. To get there: 1. From the staff interface's main page, search for a common partial name in the Check out search bar at the top of the page (e.g. mar) to get more than one result. --> No phone number column 2. Click the 'Columns' button at the top of the table --> No phone number option This table is customizable in Administration > Table settings > Patrons > Page: members > memberresults Note that table_borrowers still exists, and still has the phone number option Administration > Table settings > Circulation > Page: circulation > table_borrowers >From bug 30068, it seems it is the table in the holds patron search. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 35996] New: Add clarification to POD in writeoff_debts.pl
by bugzilla-daemon＠bugs.koha-community.org 28 May '24

28 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35996 Bug ID: 35996 Summary: Add clarification to POD in writeoff_debts.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: matt.blenkinsop(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 30324] New: Parent and child itemtype checkout limits not enforced as expected
by bugzilla-daemon＠bugs.koha-community.org 28 May '24

28 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30324 Bug ID: 30324 Summary: Parent and child itemtype checkout limits not enforced as expected Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com Depends on: 21946 When creating rules or parent and child item types, checkout limits are enforced confusingly. To recreate: 1: have an itype BK 2: create an itype BK2, set BK as the parent to BK2 3: create a circ rule for All Patrons, item type BK (displays as "Books (All)" in the circ rules interface), setting total checkouts to 1 4: do not create any rule specifically for the BK2 itype 5: have some BK items and some BK2 items 6: check a BK item out to a patron 7: check a BK2 item out to the same patron, observe you are not blocked from doing so 8: try to check out a second BK2 item to the same patron, get message "Too many checked out. 1 checked out, only 1 are allowed." 9: try to check out a second BK item to the same patrons, get message "Too many checked out. 2 checked out, only 1 are allowed." 10: return both items 11: check a BK2 item out to your patron 12: try to check a BK item out to your patron, get message "Too many checked out. 1 checked out, only 1 are allowed." We're somehow not enforcing parent/child rules reciprocally. That forces me to explicitly define my child checkout limit, defeating some of the point of the enhancement from bug 21946. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21946 [Bug 21946] Group circulation by item type -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 22613] New: Add /patrons/patron_id/checkouts endpoints
by bugzilla-daemon＠bugs.koha-community.org 28 May '24

28 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22613 Bug ID: 22613 Summary: Add /patrons/patron_id/checkouts endpoints Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com Target Milestone: --- As described in RFC, there should be endpoint in the form /patrons/{patron_id}/checkouts for getting patrons checkouts. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 48

[Bug 36160] New: Use $builder->build_object when creating patrons in Circulation.t
by bugzilla-daemon＠bugs.koha-community.org 28 May '24

28 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36160 Bug ID: 36160 Summary: Use $builder->build_object when creating patrons in Circulation.t Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Since Patron::update_lastseen was introduced in Bug 15504 circulation tests can protentially crash with: "Invalid value passed, borrowers.updated_on=SCALAR(0x564a85c3e9b0) expected type is datetime" depending of the value of TrackLastPatronActivityTriggers. This probably does not happen on a fresh Koha installation, but did when I ran the tests locally with "Renew an item" activated for TrackLastPatronActivityTriggers. The reason is that in the Circulation.t tests patron objects are created through Koha::Patron->new instead of using the builder object, and $self->lastseen($now)->store; is called in update_lastseen, on an object that does not have a valid updated_on, resulting in an invalid default value being assigned inKoha/Schema/Loader/mysql.pm. Possible added future test might also crash if resulting in these patron objects being updated. This patch fixes this issue, the tests still fail for other reasons: # Failed test 'transferbook tests' # at t/db_dependent/Circulation.t line 5769. Exception 'Koha::Exceptions::MissingParameter' thrown 'The to parameter is mandatory' But will create another issue for this if not due to some strange local issues. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 36652] New: Cannot copy notice from one branch to another
by bugzilla-daemon＠bugs.koha-community.org 28 May '24

28 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36652 Bug ID: 36652 Summary: Cannot copy notice from one branch to another Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Go to Tools > Notices and slips 2. Pick any notice and try to copy it to another library using the 'Copy notice' column. 3. You are redirected to a blank screen and if you go back to the Notices and slips page the notice has not been copied. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 36265] New: Bigger font-size for headers in staff interface
by bugzilla-daemon＠bugs.koha-community.org 28 May '24

28 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36265 Bug ID: 36265 Summary: Bigger font-size for headers in staff interface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In staff interface, text in nav bar and search header are at normal size. Since these are used a lot, I propose to increase font-size. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 36075] New: Add API route to list recalls
by bugzilla-daemon＠bugs.koha-community.org 28 May '24

28 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36075 Bug ID: 36075 Summary: Add API route to list recalls Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz CC: tomascohen(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14