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

[Bug 25983] New: Accessibility: 2.4.7 Focus Visibility
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '24

15 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25983 Bug ID: 25983 Summary: Accessibility: 2.4.7 Focus Visibility 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 purpose of this success criterion is to help a person know which element has the keyboard focus. It must be possible for a person to know which element among multiple elements has the keyboard focus. If there is only one keyboard actionable control on the screen, the success criterion would be met because the visual design presents only one keyboard actionable item. Where the success criterion says “mode of operation”, this is to account for platforms which may not always show a focus indicator. In most cases, there is only one mode of operation so this success criterion applies. https://www.w3.org/WAI/WCAG21/Understanding/focus-visible.html -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 28000] New: Locking expired patrons via cronjob should have a switch to remove holds/article requests
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '24

15 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28000 Bug ID: 28000 Summary: Locking expired patrons via cronjob should have a switch to remove holds/article requests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 21549 introduces 'LockExpiredDelay' - I think there should be a second pref 'RemoveRequestsWhenLocking' to allow the library to decide whether hold/article requests are removed when locking -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 31579] New: Improve reserve/request.pl to avoid mistakes with pick up locations
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31579 Bug ID: 31579 Summary: Improve reserve/request.pl to avoid mistakes with pick up locations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the place hold page reserve/request.pl, there are two sections. One is the "Hold details" section which allow for record hold. The other is "Place a hold on a specific item" which speaks for itself. The pick-up location by default is the signed-in user (the employee). But it is different from the "Allowed pick-up location" for the item which defaults to the homebranch. The wording should be "Pick-up location", btw, the "Allowed" states there's a list, not that the user should select it. A common tread is that the user comes in, select the pick up location in the record section, select an item *and doesn't modify the last column*, which overrule the pickup location in the notice. We propose a patch where a modification of the first drop down in the record modifies all the items dropdown to the same value by default. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 29700] New: Koha performs a second cashup in error when changing registers immediately after cashup
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29700 Bug ID: 29700 Summary: Koha performs a second cashup in error when changing registers immediately after cashup Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com To recreate: - perform a cashup for library A, register A - after cashup, koha takes you do /cgi-bin/koha/pos/register.pl?op=cashup - from that url, click to Set Library - Change yourself to library B and register B - koha takes you back to /cgi-bin/koha/pos/register.pl?op=cashup, this time for your new register, and performs a second cashup -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 28406] New: Point of sale don't register a sale when total amount is 0
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28406 Bug ID: 28406 Summary: Point of sale don't register a sale when total amount is 0 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Is that a valid use case? Likely. - For free stuff where it's useful to track the "sales" like for stock management or just to know the sold quantity as a stat. - Some real use: http://irc.koha-community.org/koha/2021-05-19#i_2353796 ==Test plan== 1. Try to sell with debit type item with price 0.00 2. Submit 3. page refreshes but no sign of a transaction 4. Register details show nothing either -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 28164] New: Sorting on POS register details transactions table is not working right
by bugzilla-daemon＠bugs.koha-community.org 14 Aug '24

14 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28164 Bug ID: 28164 Summary: Sorting on POS register details transactions table is not working right Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com Sorting on the transactions table on the point of sales register details page doesn't appear to work correctly. - Make some transactions in the points of sale page - Go to the register details page - Try to sort on the different columns - Only the price column will (partially?) sort - There is also sorting on the Actions columun -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 30519] New: Regression: using sys pref CircConfirmItemParts prevents checkin from moremember.pl and circulation.pl
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '24

13 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30519 Bug ID: 30519 Summary: Regression: using sys pref CircConfirmItemParts prevents checkin from moremember.pl and circulation.pl Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com With the addition of bug 25261, utilizing the sys pref CircConfirmItemParts and materials specified 952$3, you can no longer use the Check In column on either the morememeber.pl or circulation.pl. To test: --set sys pref to require confirmation --add a materials specified note to an item --check item out to a patron, confirming the note --go to patron record, either moremember or circulation --using the Check In column, attempt to check in the item --notice no confirmation box, and item is not checked in -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 31506] New: Add "backup days" to /etc/koha/koha-common.conf
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '24

13 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31506 Bug ID: 31506 Summary: Add "backup days" to /etc/koha/koha-common.conf Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com koha-run-backups takes the --days argument to say how many days of backup we should keep around. The value of this is set to two in the default /etc/cron.daily/koha-common that is installed by the Debian packages. I routinely increase this value to keep more backup. One thing that can happen now is that I want to create fresh backups for all the sites on a server before doing an upgrade. So I run koha-run-backups manually, but I forget about the --days argument. Result: I loose a lot of backup! It would be nice if the default for --days could be set somewhere like /etc/koha/koha-common.conf. That way we could run koha-run-backups both from cron and manually, without the --days argument, and keep the same amount of backups either way. If --days is given as an argument, it should override the default. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 27893] New: Delete of biblio with order does not always warn
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '24

09 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27893 Bug ID: 27893 Summary: Delete of biblio with order does not always warn Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: emma.ternrud(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When a biblio with a linked order gets deleted you can not cancel the order. There are two methods to delete a biblio: - Delete record in the edit menu - A check box when deleting all items using the batch deletion (see test plan). The first method generates a warning message and the second method deletes with out warnings. There should be warnings in both cases. Test plan: 1. Find a biblio with a linked order and at least one item. 2. Mark all items and press "Delete selected items". 3. At the Batch deletion page mark "Delete records if no items remain". 4. The items and the biblio will be removed without warnings. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 57

[Bug 20289] New: Unhelpful message on sip overdrive - Overdue items
by bugzilla-daemon＠bugs.koha-community.org 09 Aug '24

09 Aug '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20289 Bug ID: 20289 Summary: Unhelpful message on sip overdrive - Overdue items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When the catalog blocks checkouts if the patron has overdue items, the message is: Library server message - Greetings from Koha. For other blocks, Koha generates a more helpful message: Fines over $5 generates the following message: Library server message - Greetings from Koha. -- Patron owes 5.01 Expired patron: Library server message - Greetings from Koha. PATRON EXPIRED Invalid Password Library server message - Greetings from Koha. -- Invalid password It would be great if this could be a more consistent and helpful message for patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5