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

[Bug 36063] New: Add Holds to Pull info to intranet-main page
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36063 Bug ID: 36063 Summary: Add Holds to Pull info to intranet-main page 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We often use JS to add a display to the intranet-main page when there are holds to pull. It would be nice to just add that into Koha. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 46

[Bug 36644] New: Add option for 'Holds per item group' to circulation rules
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36644 Bug ID: 36644 Summary: Add option for 'Holds per item group' to circulation rules 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: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Not sure if this was a staff interface or hold request bug, so took a stab at it. We need a bit more granularity to hold policy on circulation rules for libraries using item group holds. Currently, libraries can only specify 'holds per record' in circulation rules, which is not a one-size-fits-all-holds solution - if they generally only want patrons to have one hold on a record for, say, books, but their manga collection is also a book item type, they have to set Holds per record (count) to a high or unlimited threshold to accommodate group holds. It would be great if circ rules could indicate a limit to holds per item group to give libraries flexibility in using item groups; many libraries probably only want one hold per item group, but they may have a collection where patrons can make multiple requests per group. Circ rules are a logical place to set this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 21459] New: Allow migrating requests between ILL and purchase suggestions
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21459 Bug ID: 21459 Summary: Allow migrating requests between ILL and purchase suggestions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no One library would like to be able to take a purchase suggestion and turn it into an ILL request. And to take an ILL request and turn it into a purchase suggestion. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 16773] New: Deleting an EDIFACT message should ask for confirmation
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16773 Bug ID: 16773 Summary: Deleting an EDIFACT message should ask for confirmation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When deleting an EDIFACT message, it should ask for confirmation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 20252] New: If an EDI orderline is cancelled send a cancellation message
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20252 Bug ID: 20252 Summary: If an EDI orderline is cancelled send a cancellation message Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: colin.campbell(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org On cancelling a order if the order has been submitted as an edifact order an ORDCHG message should be generated and transmitted. ORDCHG will contain the order reference and the ean for the item -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 33259] New: Optionally set SameSite attribute of cookie to Strict
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33259 Bug ID: 33259 Summary: Optionally set SameSite attribute of cookie to Strict Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSi… We should offer a system preference so that libraries who'd like to increase their security can set the SameSite attribute of the session cookie to Strict, rather than the default Lax. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 103

[Bug 25586] New: Something wrong with KOHA_HOME
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25586 Bug ID: 25586 Summary: Something wrong with KOHA_HOME Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 34808] New: Batch Patron Modification Tool - Select all / clear all does not select/clear all
by bugzilla-daemon＠bugs.koha-community.org 14 Oct '26

14 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34808 Bug ID: 34808 Summary: Batch Patron Modification Tool - Select all / clear all does not select/clear all 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: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Open the Batch Patron Modification Tool 2. Insert or open a file with 25+ card numbers or borrower numbers to modify then click on continue. 3. Notice that there are 2 or more pages of entries showing. If you click on clear all, it will only clear entries 1-20 but not anything on the second page (21-...). Similarly if you clear both pages and try to select all, it will only select the entries on the page you are viewing. It would useful if the select all/clear all worked on all entries. Especially for libraries that are modifying hundreds of patrons. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 34597] New: Expired patrons can still place ILL requests through OPAC
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '26

13 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34597 Bug ID: 34597 Summary: Expired patrons can still place ILL requests through OPAC Change sponsored?: --- Product: Koha Version: master 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)ptfs-europe.com CC: katrin.fischer(a)bsz-bw.de, magnus(a)libriotech.no, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com Noticed this, not sure if very severe or not. But I wonder if placing an ILL request should be included in BlockExpiredPatronOpacActions. To reproduce, on k-t-d: 1) Enable ILLmodule and install FreeForm, run: bash <(curl -s https://raw.githubusercontent.com/ammopt/koha-ill-dev/master/start-ill-dev.…) 2) Make koha/koha user expired, run mysql-kohadev: update borrowers set dateexpiry = '2020-12-31' where borrowernumber=51; 3) Visit OPAC/cgi-bin/koha/opac-user.pl and verify there's a user expired notification 4) Visit OPAC/cgi-bin/koha/opac-illrequests.pl and create a new ILL request 5) It's created with no issue -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 53

[Bug 25465] New: Batch delete records based on imported MARC batch
by bugzilla-daemon＠bugs.koha-community.org 13 Oct '26

13 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25465 Bug ID: 25465 Summary: Batch delete records based on imported MARC batch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Various vendors send libraries batches of MARC records for deletion -- these are records the library already has in their system that should be deleted as the vendor no longer offers them. Right now we can: - stage the batch for import using a matching rule - run a report to return matched biblionumbers - batch delete based on the report output It'd be great to streamline this. My two thoughts are either we could add a new option to batch record deletion to allow use of an imported file to identify records OR we could add a new matching behavior of "delete matched record" to the batch staging tool. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2