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

[Bug 20817] New: Acquisitions development - Ordering existing items
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '26

10 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20817 Bug ID: 20817 Summary: Acquisitions development - Ordering existing items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: kyle(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Acquisitions: attaching orders to existing records while retaining 9xx information. -- You are receiving this mail because: You are watching all bug changes.

1 162

[Bug 17506] New: Offline circ needs to be logged
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '26

10 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17506 Bug ID: 17506 Summary: Offline circ needs to be logged 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com I recently spent about an hour and a half going over logs trying to figure out why old checkouts were showing up on patron records, and the logs were not lining up. We finally came to the assumption that someone uploaded an old offline circ file. Unfortunately, there is nothing in the logs to record offline circ transactions, and nothing tied to the specific checkouts either. It would REALLY be helpful if the logs would record offline circ transactions, including date of upload, and date of the transaction. It would also be helpful if the item history would indicate a transaction through offline circ and when the transaction was processed. It would be really cool if I could get that hour and a half back. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 16839] New: Sort Title (A-Z) doesn't work with some non-latin alphabets
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '26

10 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16839 Bug ID: 16839 Summary: Sort Title (A-Z) doesn't work with some non-latin alphabets Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 53036 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=53036&action=ed… View of ordered results under ICU Using ICU or not the sorting of a list of results in opac/staff client is ineffective for character sets such as cyrillic Without ICU the sorting seems to be by length -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 18922] New: Mana - Share review
by bugzilla-daemon＠bugs.koha-community.org 10 Mar '26

10 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18922 Bug ID: 18922 Summary: Mana - Share review Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org This module add reviews for Mana -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 30657] New: Make patron attributes available via Template Toolkit in overdues
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30657 Bug ID: 30657 Summary: Make patron attributes available via Template Toolkit in overdues 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using Template Toolkit to fetch patron values, one should be able to fetch patron attribute values. This would be useful both for printing those values into the notice content and for using those values in logic to vary the notices per patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 78

[Bug 28527] New: Transfers that are cancelled whilst in transit should still appear as 'in transit' until they are received
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28527 Bug ID: 28527 Summary: Transfers that are cancelled whilst in transit should still appear as 'in transit' until they are received Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If a transfer is cancelled whilst it is in transit (datesent set, but datearrived not) then we should still return it as in transit. Bug 27993 added a condition to the 'in_transit' boolean which should be reverted. We should also update the get_transfer (and get_transfers) methods to catch such cases and return those still active transfers and deal with them appropriately at check-in. (i.e. invoke the reverse transfer or pick the next transfer from the queue and notify the librarian of what subsequent actions they should take). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 28761] New: Item status shows incorrectly on opac-course-details.pl
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28761 Bug ID: 28761 Summary: Item status shows incorrectly on opac-course-details.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: - create a course in course reserves, add an item to it. - confirm your item shows Available for its status on opac-course-details.pl - give your item a notforloan status - reload opac-course-details.pl, confirm its still "available" - give your item a restricted user status - reload opac-course-details.pl, confirm its still "available" - give your item a lost, damaged, or withdrawn status - reload opac-course-details.pl, these statuses *are* reflected Filing a separate bug for the staff client. -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 30533] New: Add exact search option for patrons
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30533 Bug ID: 30533 Summary: Add exact search option for patrons 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com A patron search for names like "JOHN JOHNSON" ends up getting parsed something like "WHERE surname like "%JOHN%" OR firstname like "%JOHN%" OR surname like "%JOHNSON%" OR firstname like "%JOHNSON%"" and finds a really unhelpfully large pile of patrons. Bug 17500 suggests implementing Elastic for patron searching, which would be great. In the meantime, we could give a little help for searches like this by giving an exact search option -- so the query would parse more or less the same but without the wildcards. That's also a problematic search for many situations, but would work better here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 33200] New: IndependentBranchesTransfers does not prevent holds from creating transfers
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33200 Bug ID: 33200 Summary: IndependentBranchesTransfers does not prevent holds from creating transfers Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 I noticed that when you have IndependentBranches (Yes), IndependentBranchesTransfers (Yes), and canreservefromotherbranches (Don't allow), holds can still trigger transfers. This is probably larger than transfers as holds should not be placed on items from other libraries with IndependentBranches, even if we choose "next available item". IndependentBranches/canreservefromotherbranches should imply "next available item (from this branch)". To reproduce, you must have - IndependentBranches, IndependentBranchesPatronModifications and IndependentBranchesTransfers preferences set to Yes - canreservefromotherbranches must be set to Don't allow - Circulation rules that allow holds and checkouts - Two libraries (I used Midway (A) and Centerville (B)) - A record with two items, one at each library, with barcodes, check out the one from library A - Two non-superlibrarian staff user, one in each library, with at least catalogue and holds permissions, this is what I gave them - circulate (all) - catalogue - delete_borrowers - edit_borrowers - reserveforothers (all) 1. Log in to the staff interface with the non-superlibrarian staff user from library A 2. Go to the record with the two items, click "Place hold" 3. Place a hold for a user, without changing anything (should be for "next available item") 4. Log out and log back in with the non-superlibrarian staff user from library B 5. Check in the item from library B, which should be available --> Hold is confirmed for patron from library A, transfer is created 6. Optionally, you can log out and log back in as staff from library A 7. Go to Circulation > Transfers to receive (should this even be available with IndependentBranchesTransfers turned on?) --> Item from other branch is there -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 51

[Bug 31504] New: ElasticSearch No indexing new records after upgrade
by bugzilla-daemon＠bugs.koha-community.org 09 Mar '26

09 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31504 Bug ID: 31504 Summary: ElasticSearch No indexing new records after upgrade Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: hagud(a)orex.es After upgrading koha 21.11 to 22.05 ElasticSearch is not able to index new records. At webadmin we can see the warning 'Index 'koha_xxxxxx' needs to be recreated.' Executing 'Reset mapping' button doesn't fix the error... when trying to full reindex with option -d or -r it doesn't work admin@___21:~$ sudo koha-elasticsearch --rebuild -d ___ sudo: unable to resolve host ___21: Name or service not known sudo: unable to resolve host ___21: Name or service not known Use of uninitialized value $reason in concatenation (.) or string at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/Indexer.pm line 283. Exception 'Koha::Exception' thrown 'Unable to update mappings for index "koha_____biblios". Reason was: "". Index needs to be recreated and reindexed' Something went wrong rebuilding indexes for ___ Removing the index directly at ElasticSearch doesn't works * ElasticSearch is not localhost -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13