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

[Bug 33446] New: Revert transit status should have the option to cancel the item transfer as well
by bugzilla-daemon＠bugs.koha-community.org 12 May '26

12 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33446 Bug ID: 33446 Summary: Revert transit status should have the option to cancel the item transfer as well 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: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Currently, when a hold's transit status is reverted, the item remains in-transit until the transfer is completed by a check-in. This makes sense if the item actually is still in-transit, but there are other situations in which this transit status is incorrect and may not be easy to remove. For example, in our system, we have HoldsAutoFill enabled. Occasionally there are exceptions where we don't want a book to be put in transit for a hold, but instead to remain available at its home branch. If the staff member reverts the transit status on the hold, the item still shows as In Transit. But they can't check in the item to complete the transfer without causing the hold to trap again. In this situation, the book shouldn't be showing as In Transit, but there's no simple way to remove that status. It's several extra steps at best to manually cancel the transfer (and most of our staff don't know how to do this, as manual transfers are not a normal part of our workflow, so many items retain an incorrect "In transit" status indefinitely). When a hold's transit status is reverted by the sending librarian because they're not planning on sending the book for whatever reason, it would be great if they could revert the hold transit status and cancel the item transfer all in one step. This could be something as simple as a checkbox option or a drop-down, so that the user can choose between "Revert transit status" versus "Revert transit status and cancel item transfer". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 22322] New: Self-checkin module should provide for automatic logins (like self-checkout)
by bugzilla-daemon＠bugs.koha-community.org 12 May '26

12 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22322 Bug ID: 22322 Summary: Self-checkin module should provide for automatic logins (like self-checkout) 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: oliver.behnke(a)aei.mpg.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- The self-checkin (SCI) module currently requires to set up a dedicated kiosk terminal for its purpose. The reason being that you can't provide user/password system preferences for an automatic login, like you can for the self-checkout (SCO) counterpart. Our use case is the following: we are already using the SCO module with automatic login of the dedicated SCO patron, and our actual patrons identify themselves via their cardnumber. While they can obviously check in their books via the SCO module, we'd like to streamline the process such that they don't have to login with their cardnumber in order to simply return a book. The SCI module would be ideal for this but, effectively, it can't be used on the same terminal as switching between the modules currently requires a manual login of the dedicated SCI patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 58

[Bug 16260] New: Moderate the impact of AllowHoldsOnPatronsPossessions
by bugzilla-daemon＠bugs.koha-community.org 11 May '26

11 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16260 Bug ID: 16260 Summary: Moderate the impact of AllowHoldsOnPatronsPossessions 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: marjorie.barry-vila(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Hi, System preference AllowHoldsOnPatronsPossessions is too restrictive. Test plan: -AllowHoldsOnPatronsPossessions : Don't allow -notice with 2 items (X and Y) -one of items is check-out by borrower A (item X) -other items is check-out by borrower B (item Y) If Borrower A wants to hold item Y, he can not because of the system preference. If system preference is Allow, Borrower A can hold item Y but he can hold item X too, and we don't want that he can. Is there something I do not understand in the configuration ? Regards, Marjorie -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 35114] New: Total on basketgroup can be different than basket details total
by bugzilla-daemon＠bugs.koha-community.org 11 May '26

11 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35114 Bug ID: 35114 Summary: Total on basketgroup can be different than basket details total Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Hello :) This patch aims rather to clarify and avoid display errors concerning the total of the basket. When totals are displayed on the basketgroup.pl view the total is calculated relative to the rounded estimated cost (ecost) - tax included or excluded. While on the basket.pl view in detail, the logic is to take the unit price (tax included or excluded) OR then the estimated cost - tax included or excluded. This can cause a slight difference of cents depending on whether the unit price is calculated or not compared to the estimated price calculated. All this depending on the rounding or not of the third decimal for the fields not calculated (OrderPriceRounding activated or not). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 27248] New: Allow to use list of barcodes/itemnumbers with Batch extend due dates tool
by bugzilla-daemon＠bugs.koha-community.org 11 May '26

11 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27248 Bug ID: 27248 Summary: Allow to use list of barcodes/itemnumbers with Batch extend due dates tool Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org In some cases libraries want to use some more complicated criteria for selecting the items that they want to extend the due dates for. For these cases it would be great if SQL reports could be used to make a list that then can be uploaded to the tool, similar to how we manage other batch operations. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 21156] New: Internationalization: plural forms, context, and more for JS files
by bugzilla-daemon＠bugs.koha-community.org 11 May '26

11 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21156 Bug ID: 21156 Summary: Internationalization: plural forms, context, and more for JS files Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Depends on: 15395 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15395 [Bug 15395] Internationalization: plural forms, context, and more -- You are receiving this mail because: You are watching all bug changes.

1 78

[Bug 27978] New: Marc modification templates should allow for copying an entire field to a field/subfield and vice versa
by bugzilla-daemon＠bugs.koha-community.org 09 May '26

09 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27978 Bug ID: 27978 Summary: Marc modification templates should allow for copying an entire field to a field/subfield and vice versa 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently you are limited to copying from a field/subfield to another field/subfield This prevents operations like copying from a subfield into a control field and vice versa see bug 9921 for an example of a desired behavior biblionumber into control field -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 32750] New: Additional fields: Allow fields to be marked as mandatory
by bugzilla-daemon＠bugs.koha-community.org 09 May '26

09 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32750 Bug ID: 32750 Summary: Additional fields: Allow fields to be marked as mandatory Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, michaela.sieber(a)kit.edu It would be nice if additional fields could be marked as mandatory. This would add the "required" to the forms where the data is entered/edited, enforcing that data is entered before the record can be saved. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 30815] New: Use of uninitialized value $charge in numeric gt (>) at /usr/share/koha/lib/C4/Circulation.pm
by bugzilla-daemon＠bugs.koha-community.org 09 May '26

09 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30815 Bug ID: 30815 Summary: Use of uninitialized value $charge in numeric gt (>) at /usr/share/koha/lib/C4/Circulation.pm Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Blocks: 25798 The code on 20.11.17 is: # Charge a new rental fee, if applicable my ( $charge, $type ) = GetIssuingCharges( $itemnumber, $borrowernumber ); if ( $charge > 0 ) { AddIssuingCharge($issue, $charge, 'RENT_RENEW'); } But it's the same on current master. The line given is the if-clause in line 3171. The default for rentalcharge and rentalcharge_daily in itemtypes is NULL, maybe that's the cause? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25798 [Bug 25798] Copyright year to Holds to pull report -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 35630] New: Add ability to log changes to Authorized Values
by bugzilla-daemon＠bugs.koha-community.org 09 May '26

09 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35630 Bug ID: 35630 Summary: Add ability to log changes to Authorized Values 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: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With the increase in number of authorized values, and with the newer sys pref CreateAVFromCataloguing, it is becoming essential to be able to determine who/when/how changes are made to authorized values, and this not currently being logged. It would be a great help to be able to log these changes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37