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

[Bug 9810] Search limit 'available' does not hide damaged, withdrawn, or not-for-loan items
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9810 carthur(a)slolibrary.org <carthur(a)slolibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carthur(a)slolibrary.org -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38452] New: Inventory tool barcodes should not be case sensitive
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38452 Bug ID: 38452 Summary: Inventory tool barcodes should not be case sensitive Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org I say this because it doesn't appear like we honor case sensitivity for barcodes elsewhere. So, to recreate: 1. Create an item give it a barcode like 'abc123'; 2. Try creating a 2nd item with a barcode: 'ABC123', you get an error 'Error saving item: Barcode must be unique.' 3. Checkin the item 'ABC123', the 'abc123' item successfully checks in. 4. The case doesn't seem to matter elsewhere in Koha ( check-in, checkout, searching, batch tools ) 5. Try the inventory tool and use 'ABC123'. The barcode is not found. If Koha treats 'ABC123' and 'abc123' the same when creating an item, it should probably treat them the same when using the inventory tool. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 39889] New: Budgets.t is missing it's rollback
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39889 Bug ID: 39889 Summary: Budgets.t is missing it's rollback Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org We're missing the final rollback in Budgets.t and thus when run it removes all budgets from the database perminently causing subsequent unit tests to fail. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 29985] New: Cashup summary shows unexplainable odd amounts
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29985 Bug ID: 29985 Summary: Cashup summary shows unexplainable odd amounts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major 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 I performed some transactions testing bug 27779 in a fresh ktd instance. I used amounts like 4.50 or 10.00 or 1.55, nothing with more decimals, but I still ended up with this: Cash register: This is a register. Period: to 2022-01-31 21:22:40 Type Total Total 0.0499999999999998 Cash -0.0499999999999998 I have no idea how this can happen, since all amounts in my accountlines and account_offsets are only in 5 cent steps. With the patch from 27779 applies it also shows even amounts: Cash register: This is a register. Period: to 2022-01-31 21:22:40 Type Total Refund against Manual fee - 6 Refund against New card fee - 6 Manual fee 4.55 USB Stick 1.5 Total 0.0499999999999998 Cash -0.0499999999999998 As this should only be additions/subtractions, I have no idea how this could happen unless we have a bug somewhere? Also display should be using Price (CurrencyFormat) system preference, but it doesn't, display remains unchanged with FR option. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 13985] [Omnibus] Cash Management - Koha as 'Point of Sale'
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13985 Bug 13985 depends on bug 29985, which changed state. Bug 29985 Summary: Cashup summary shows unexplainable odd amounts https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29985 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 31045] New: Add a housebound notification to staff interface
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31045 Bug ID: 31045 Summary: Add a housebound notification to staff interface Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: estherm(a)sodaspringsid.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Similar to the notification for curbside pickup or purchase suggestions, it would be nice to add a housebound delivery notification reminder. Otherwise staff would need to know, remember, or otherwise maintain a list of patrons who need housebound services outside of Koha. If combined with bug 26545 where patrons can update info or request a delivery through the OPAC, the overall module becomes much more useful. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 39770] New: Limiting subtypes by Braille doesn't work when searching with ElasticSearch
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39770 Bug ID: 39770 Summary: Limiting subtypes by Braille doesn't work when searching with ElasticSearch Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: stalkernoid(a)gmail.com Reporter: stalkernoid(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: nugged(a)gmail.com, slavashishkin(a)gmail.com When trying to use ElasticSearch to find books that have Braille it doesn't find anything: No results match your search with limit(s): 'ff7-01-02:("tc or fb")'. To reproduce: 1. Have ElasticSearch enabled and you have books that have books with braille, or make up one yourself by adding "tc" (text - Braille) or "fb" (tactile material - braille) to 007 MARC field. 2. Go to catalogue/advanced search and select format: braille from the dropdown. 3. Try to find anything, if you are using ElasticSearch you will see: No results match your search with limit(s): 'ff7-01-02:("tc or fb")' -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 15516] Allow to place a hold on first available item from a group of titles
by bugzilla-daemon＠bugs.koha-community.org 13 May '25

13 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15516 --- Comment #478 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Andrew Fuerste-Henry from comment #477) > (In reply to Magnus Enger from comment #476) > > Lots of history here... Can I ask what the status is? Is anyone planning to > > continue working on this? > > ByWater / Open Fifth are working on this with a partner library! I'm currently running this in production for one of our libraries. It would be great if Bywater/OpenFifth could loop me in on this one, since it would be suboptimal to have 2 different competing features. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 30380] New: No suggestions ASKED letter transported by email
by bugzilla-daemon＠bugs.koha-community.org 12 May '25

12 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30380 Bug ID: 30380 Summary: No suggestions ASKED letter transported by email 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org C4/Suggestions line 487 calls GetPreparedLetter with status==ASKED in the letter code parameter, causing warning at line 583 in C4/Letters: No suggestions ASKED letter transported by email Since we have no ASKED notice, we should either check the status and not call Letters or add this notice. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 38396] New: Revert transit status on a hold does not work
by bugzilla-daemon＠bugs.koha-community.org 12 May '25

12 May '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38396 Bug ID: 38396 Summary: Revert transit status on a hold does not work Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: bdaeuber(a)cityoffargo.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Click the "revert transit status" on a hold allows you to change the pickup location of the item, but the item stays in transit. To recreate: 1. Place a hold for pickup at a different location. 2. Check in the hold to trigger the transfer to the pickup location. 3. Go to the holds table and click "revert transit status" on the hold. Change the location if you wish. 4. Return to the record and note that the item still says it's in transit to the original location. Checking in the location does transfer it properly, but the transit status should actually reset. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6