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

[Bug 28539] New: allow for negative payments in Point of Sale
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '26

25 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28539 Bug ID: 28539 Summary: allow for negative payments in Point of Sale Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: technology(a)haineslibrary.org QA Contact: testopia(a)bugs.koha-community.org Enhancement request: Allow for negative payments in Point of Sale. In Point of Sale module, you are allowed to edit the cost of a sale item, and change the amount tendered. But the system won't allow you to input negative numbers for cost. For example, if we want to refund a patron $20 from their print account, we take $20 out of the register and hand it to the patron. Point of Sale has no way to record this refund, since the money was collected long ago and over many transactions (i.e. there is no specific transaction to refund). As a result, the register in POS will be over by $20. If we could make a sale of an item with a cost of -20.00, we could account for this refund and balance the POS register correctly. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 35830] New: Add separate permission for Merging Patrons
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '26

25 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35830 Bug ID: 35830 Summary: Add separate permission for Merging Patrons Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: rcoert(a)arlingtonva.us QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, the ability to Merge Patrons is lumped under the "Add, modify, and view patron information" (edit_borrowers). Merging patron records is more powerful than the ability to add/modify/view a patron record. My request is to have this as a separate permission, similar to that of delete_borrowers. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 31118] New: Allow to send the TOTP token when enabling 2FA
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '26

25 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31118 Bug ID: 31118 Summary: Allow to send the TOTP token when enabling 2FA Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Depends on: 28787 Bug 28787 adds the ability to send the token by email on login, but it would be great to have it available when we enable 2FA as well. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28787 [Bug 28787] Send a notice with the TOTP token -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 35210] New: 2FA: more flexibility
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '26

25 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35210 Bug ID: 35210 Summary: 2FA: more flexibility Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: rebecca.bradshaw(a)nnuh.nhs.uk QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Would it be possible for the 2FA to have more flexibility thank it currently does. At the moment staff need to set it up via a phone and a QR code, once this is set up there is an option to have the code emailed which is great but it does ask for 2FA each time they login. This is not helpful. Is there functionality for the 2FA to ask once a week or once a day/if signing in on a different comuputer/device? Thanks! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 28437] New: Provide 'print' as an option for patron messaging
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '26

25 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28437 Bug ID: 28437 Summary: Provide 'print' as an option for patron messaging Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org While 'Hold ready' and 'Overdue' notices fallback to print, other patron messages cannot be selected with 'print' as the message transport. Users can, however, define print notices for any letter code, indicating they are an option to generate. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 38174] New: Self Checkout renders alert for each checkout in session instead of just most recent checkout
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '26

25 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38174 Bug ID: 38174 Summary: Self Checkout renders alert for each checkout in session instead of just most recent checkout Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: blawlor(a)clamsnet.org QA Contact: testopia(a)bugs.koha-community.org In self checkout, if a patron scans a stack of books one at a time, an additional blue alert-info box is rendered for each new checkout. When this list becomes long it can push the barcode input down so far that it goes off screen which can be confusing for patrons. When not using batch checkout, self checkout should only render an alert-info box for the most recent scan. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 37286] New: Fix REST API authentication when using Mojo apps
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '26

25 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37286 Bug ID: 37286 Summary: Fix REST API authentication when using Mojo apps Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: REST API Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Koha::REST::V1::Auth checks the request URL path and do various things depending on how it looks. For instance, it allows everyone to access paths starting with "/api/v1/oauth/" But because of how Koha::REST::V1 was written, when using mojolicious applications Koha::App::Intranet and Koha::App::Opac, paths had to add a path prefix ("/api"), which means the final path as seen by Koha::REST::V1::Auth looked like this: "/api/api/v1/oauth" I said "had to", but actually there is another way that does not require this path manipulation and that's what this bug is about -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 36365] New: compare-es-to-db tool should offer a mode to reconcile differences
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '26

25 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36365 Bug ID: 36365 Summary: compare-es-to-db tool should offer a mode to reconcile differences Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P3 Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Koha can currently tell how many biblios are in the database vs how many are in the elasticsearch indexes, but it cannot reconcile those differences without either bespoke work deleting individual ES documents or a full reindex. A full reindex might not solve the problem anyway, due to invalid data in MARC records. It would be really neat if the existing tool to compare-es-to-db.pl had a mode that would at least try to reconcile any discrepancies. For example if it was discovered that there were more indexes than biblios, remove the erroneous ES documents, or if there were more biblios than es indexes, identify them and attempt to reindex them. We should also provide an easy to understand error report if reconciliation was not possible, with suggested actions to take for the sysadmins or users. This would obviously be an Elasticsearch only feature. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 37920] New: writeoff_debts.pl should be logged
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37920 Bug ID: 37920 Summary: writeoff_debts.pl should be logged Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Depends on: 27049 Runs of the writeoff_debts cron are not logged in the action logs. They should be. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27049 [Bug 27049] Add a script to bulk writeoff debts -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 31263] New: Curbside pickups - Should the patron be able to alert even if not staged
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31263 Bug ID: 31263 Summary: Curbside pickups - Should the patron be able to alert even if not staged Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 30650 The patron can alert staff of their arrival only if the pickup is "staged and ready". Is that the expected behaviour? Do we want them to be able to alert even if it's still not ready yet? Do we need a syspref (or per library, in the admin) to control that? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30650 [Bug 30650] Convert the Curbside Pickup plugin to Koha core -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8