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

[Bug 40492] New: Pending offline circulation actions - barcode link should link to item details
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '26

26 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40492 Bug ID: 40492 Summary: Pending offline circulation actions - barcode link should link to item details Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: emily.lamancusa(a)montgomerycountymd.gov Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com In the pending offline circulation actions table, the barcode links to the biblio record, but it would be more helpful if it linked to the item details of the specific item. -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 33364] New: Stop Holds to Pull report showing items that have been allocated to a recall
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '26

26 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33364 Bug ID: 33364 Summary: Stop Holds to Pull report showing items that have been allocated to a recall Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The Holds to Pull report shows an item with a hold if the item is available on the shelf, ready to pull and allocate to the hold. The Holds to Pull should NOT show an item with a hold if that item has already been allocated to a recall (i.e. the recalled item is awaiting pickup and or in transit for a patron). To reproduce: 1. Enable UseRecalls and set the recalls-related circulation rules 2. Check out an item to Patron A 3. Place a hold on the item for Patron B 4. Log into the OPAC as Patron C and search for the item. Place a recall on the item. 5. Go back to the staff interface. Go to Circulation -> Holds to pull 6. Confirm the item shows in the Holds to pull table, with the hold for Patron B 7. Check in the item and confirm the recall as waiting 8. Go back to the Holds to pull page. You could manually regenerate the page but running the cronjob in the terminal misc/cronjobs/holds/build_holds_queue.pl 9. Notice that even though the item is allocated for a recall, the hold is showing. It should not be showing in this page. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 49

[Bug 36762] New: Item not transferred correctly when there is a pending hold
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '26

26 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36762 Bug ID: 36762 Summary: Item not transferred correctly when there is a pending hold Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Koha is doing some dumb stuff when one attempts to transfer an item that could fill a pending hold. To recreate: 1 - be logged in at Branch A 2 - have a bib with 1 holdable item at Branch A 3 - place a hold for pickup at Branch B 4 - confirm hold shows on Holds to Pull and Holds Queue 5 - go to Circulation > Transfers and attempt to send your item to Branch C 6 - Koha gives you three options. Pick the first one: "Transfer to Branch B." This is the hold pickup branch, not the branch you selected for your transfer 7 - Koha tells you it has transferred the item to Branch C (the branch you did select for your transfer) 8 - go to detail.pl for your title, confirm the holdings table says "there is an item level hold" on your item 9 - click to the Holds tab for your title, confirm the hold claims to be in transit 10 - query the branchtransfers table, confirm no transfer was created 11 - query reserves and confirm your hold has found=T, itemnumber=[your item], and item_level_hold=0 12 - Back on the title, attempt to revert transit status, confirm the Revert button doesn't do anything At step 6, Koha should offer to transfer to the indicated transfer-target, rather than the hold pickup branch. Then it should actually generate the transfer and should not insert the itemnumber into the reserves table or update reserves.found. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[Bug 41084] New: Zotero connector broken by bug 37370
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '26

26 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41084 Bug ID: 41084 Summary: Zotero connector broken by bug 37370 Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Depends on: 37370 This is difficult.. as I said in the comment on bug 37370, we find libraries don't want to visually show utf8 in the export menu, but do want Zotero to work. As such, completely denying the utf8 option, which is the default fallback when no format is passed too, breaks the Zotero browser extension. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37370 [Bug 37370] opac-export.pl can be used even if exporting disabled -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 41227] New: SuspendHoldsIntranet and SuspendHoldsOPAC have no effect
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '26

26 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41227 Bug ID: 41227 Summary: SuspendHoldsIntranet and SuspendHoldsOPAC have no effect Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com It seems that no matter what the SuspendHoldsIntranet and SuspendHoldsOPAC system preferences are set to, the suspend holds column always appears in both the staff client and OPAC. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 41061] New: No longer needed to validate dates manually
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '26

26 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41061 Bug ID: 41061 Summary: No longer needed to validate dates manually Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 33703 I've tried to resurrect bug 31149 but finally realised that this code is no longer needed. I think it's coming from the introduction of Masikto by bug 33703. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33703 [Bug 33703] Entering dates should be more flexible accepting different entry formats -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 41249] New: ILL batches should be compatible with AutoILLBackendPriority
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '26

26 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41249 Bug ID: 41249 Summary: ILL batches should be compatible with AutoILLBackendPriority Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com AutoILLBackendPriority suggests the top most available backend in priority when creating a new ILL request. This should also work the same when creating requests through the ILL batches functionality. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 42

[Bug 39054] New: a need to distinguish between manual bibliographic record modifications and those being a consequence of authority modification
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '26

26 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39054 Bug ID: 39054 Summary: a need to distinguish between manual bibliographic record modifications and those being a consequence of authority modification Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Now in action_logs, Koha does not distinguish between manual bibliographic record modifications and those being a consequence of authority modification. Both are logged in the same way: module: CATALOGUING ; operation: MODIFY ; interface: intranet. IMO it would be helpful to be able to distinguish this two cases. (For instance to be able to evaluate a librarian's 'koha' in the cataloguing process: a single action of modification of one authority record launching a modification of, say, 100 bibliographic records does not equal to manual modification of 100 bibliographic records. Also, if we trace issues in bibliographic records after modification being performed and want librarians to correct themselves, a biblio modification being a consequence of an authority modification should not be taken into account. Etc.) Comment are welcome. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[Bug 38589] New: The manual should specify that MARC configuration for bundles is the same for MARC21 and UNIMARC
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '26

26 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38589 Bug ID: 38589 Summary: The manual should specify that MARC configuration for bundles is the same for MARC21 and UNIMARC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de In the manual, the item bundle section (https://koha-community.org/manual/latest/fr/html/circulation.html#circulati…) states "The bundle functionality will only be displayed if you create a catalogue record with the Leader, (000 MARC tag) position 7 set to ‘c’ for Collection." and displays a picture from MARC21 framework This exact configuration setting is working for UNIMARC ("c" in pos.7 of leader), but this is not obvious as many settings in Koha are MARC-flavour-dependant -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 37140] New: Add vendor automatically to 952 $e when creating items for serials
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '26

24 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37140 Bug ID: 37140 Summary: Add vendor automatically to 952 $e when creating items for serials Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: christian.stelzenmueller(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org On receiving a serial in the serials module, it would be helpful to add the id of the vendor automatically to the item In 952 $e (Source of acquisition), if the subscription is set to "create an item record", and the subscription has a vendor. Similar to the acquisition module, where the vendor is already added automatically to the items. To test: 1. If necessary, set 952 $e in the bibliographic framework to visible in the staff interface and the editor. 2. Go to serials 3. Create a subscription with a vendor and the setting “create an item record” and save it. 4. Go to serial collection. 5. Set a serial issue from status “Expected” to “Arrived” 6. The vendor in subfield “e” (Source of acquisition) in the item form is empty. But it would be nice if the vendor was filled in automatically. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26