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

[Bug 29393] New: Ability to send emails from patron details page
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '26

05 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29393 Bug ID: 29393 Summary: Ability to send emails from patron details page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 117

[Bug 40906] New: Change the "Create report from mana" interface, to make it look more like a plugin market place/app store
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '26

05 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40906 Bug ID: 40906 Summary: Change the "Create report from mana" interface, to make it look more like a plugin market place/app store Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Mana-kb Assignee: koha-bugs(a)lists.koha-community.org Reporter: elias.lorgnier(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: alex.arnaud(a)biblibre.com The idea is to create a better interface than search only for importing reports from mana. A marketplace would allow discovering new reports, while maintaining a good searchability. The information presented as a grid of cards would allow seeing immediately informations that are important to evaluate the relevance and "reliability" of a report : title, description, author, number of download. It would also allow for a better visual hierarchy between title, description, and other information. Each card will show the following informations - Title - Author - number of downloads - description (Note in Koha) The full SQL code from the report will be available by clicking on each card, as well as the full description of the report. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61

[Bug 37796] New: Generated issue has incorrect number in pattern when receiving
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '26

05 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37796 Bug ID: 37796 Summary: Generated issue has incorrect number in pattern when receiving Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 170927 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=170927&action=e… Incorrect number on generated issue Discovered while testing Bug 35646 To Replicate 1. Follow Bug 35646 and create a numbering pattern for {MonthName} {Year}. 2. Test the pattern for a 1/month frequency, subscription start date on the first day of the month. See that the numbering pattern increments correctly for the month names and year. 3. Find a serial in the catalog and add a new subscription. 4. On the second page of the subscription configuration, select the numbering pattern for MonthName Year. 5. Test the prediction pattern and see everything increments correctly. 6. Save the subscription. 7. Receive. See the the first issue displays correctly for the month name and year. 8. Mark the issue as arrived and generate the next issue. See the next issue does not have the correct month name and year. (image attached). 9. Mark the next issue Arrived and generate the third issue. The date published and number continue to increment incorrectly. Possibly connected to bug 20653, though this example is not irregular. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 46

[Bug 40840] New: Failure of an EDI SFTP account will kill edi_cron.pl preventing uploads from subsequent accounts
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '26

05 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40840 Bug ID: 40840 Summary: Failure of an EDI SFTP account will kill edi_cron.pl preventing uploads from subsequent accounts Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org EDI uploads are processed in order. If one account is unable to connect to the SFTP server, it will call die_on_error which kills the script. This does not affect regular FTP which will fail gracefully. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 40986] New: Add some reindexing examples to rebuild_elasticsearch.pl
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '26

04 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40986 Bug ID: 40986 Summary: Add some reindexing examples to rebuild_elasticsearch.pl Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at QA Contact: testopia(a)bugs.koha-community.org I want to document some examples of "advanced" usage of rebuild_elasticsearch.pl using --where SQL I think the best place is to add them to the POD of the script itself (because in my experience this has the highest success rate of keeping it up to date) We could then add to the docs / the wiki etc instructions on how to show this examples (i.e. `rebuild_elasticsearch.pl --help`) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 31406] New: Set focus for cursor to setSpec input when adding a new item search field
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '26

04 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31406 Bug ID: 31406 Summary: Set focus for cursor to setSpec input when adding a new item search field Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When adding a new item search field from administration, the focus/cursor should be in the first field of the entry form: Name -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 40186] New: Show additional fields in search form on acquisition start page
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '26

04 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40186 Bug ID: 40186 Summary: Show additional fields in search form on acquisition start page Change sponsored?: --- Product: Koha Version: Main 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 CC: clemens.tubach(a)kit.edu, michaela.sieber(a)kit.edu At the moment the search form on the acquisition start page and on the Advanced search page are slightly different: the first is missing the additional fields. It would be nice if the additional fields showed on both search forms or if that was configurable. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 41113] New: Missing doc-head-close and cssinclude in sci-main.tt
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '26

04 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41113 Bug ID: 41113 Summary: Missing doc-head-close and cssinclude in sci-main.tt Initiative type: --- Sponsorship Sponsored status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: aleisha(a)catalyst.net.nz, alexbuckley(a)catalyst.net.nz, dcook(a)prosentient.com.au, hammat.wele(a)inlibro.com, lucas(a)bywatersolutions.com, testopia(a)bugs.koha-community.org +++ This bug was initially created as a clone of Bug #21266 +++ Many of the some changes should be made to the self checkin templates -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 38864] New: API functionality needed in patron message to allow future connectivity with discovery systems
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '26

04 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38864 Bug ID: 38864 Summary: API functionality needed in patron message to allow future connectivity with discovery systems Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org I would like to see API functionality added for patron messages (particularly the OPAC messages) so that down the road, discovery systems like Aspen could develop more connectivity with Koha and other ILS systems to allow those messages to have the option to notify patrons on their accounts in discovery. Right now, that is a major gap when using a discovery system. We can communicate with the patron in their account in the OPAC, but not through their account in Aspen, or other third party catalogs. This would need to include a way for messages to be discovered by the discovery system and a way to set the read flag (a newer feature in Koha) so that patrons can mark the message as read and staff can see it has been read. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 24535] New: Add the ability to have longer barcodes than 20 digits
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '26

04 Nov '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24535 Bug ID: 24535 Summary: Add the ability to have longer barcodes than 20 digits Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: nick(a)bywatersolutions.com Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently, in Koha, an item's barcode can only be up to 20 digits, it would be nice to increase this value to possibly a higher number such as 32. Koha recently increased the patron's barcode length to 32 and it was helpful to libraries. -- You are receiving this mail because: You are watching all bug changes.

1 34