July 2026 - Koha-bugs - lists.koha-community.org

[Bug 42961] New: Option for no mail (-n) no longer functional in membership_expiry cron
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '26

01 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42961 Bug ID: 42961 Summary: Option for no mail (-n) no longer functional in membership_expiry cron Initiative type: --- Sponsorship --- status: 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk Depends on: 30301 Target Milestone: --- The options on the membership_expiry cron include: <-n> Do not send any email. Membership expire notices that would have been sent to the patrons are printed to standard out. Including this flag does not block the cron from enqueueing messages or cause those messages to print to standard out. It looks like the the functionality was removed by BZ 30301? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30301 [Bug 30301] Add an option to specify the patron expiration notices as mandatory by patron category -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 41493] New: Add New Item Statistical Fields
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '26

01 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41493 Bug ID: 41493 Summary: Add New Item Statistical Fields Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: trevor.diamond(a)mainlib.org QA Contact: testopia(a)bugs.koha-community.org Add more information regarding checkouts to each item. Instead of a single "checkouts" count for the entire life of the item, have a total checkouts, ytd checkouts, and maybe even a previous ytd checkouts. Seeing the recent activity can be a useful indicator when doing collection development (either adding or weeding). An item popular 4 years ago might have tons of circulation but is no longer serving the public and it hasn't been checked out a single time in the last year. Perhaps there's a new edition, perhaps something else happened. Just looking at the lifetime circ can make a title seem to have more relevance that it should. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 33758] New: Add a parameter to use the intranet_catalog_biblio_enhancements_toolbar_button Plugin hook
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '26

01 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33758 Bug ID: 33758 Summary: Add a parameter to use the intranet_catalog_biblio_enhancements_toolbar_button Plugin hook Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: nicolas.giraud(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: caroline.cyr-la-rose(a)inlibro.com, philippe.blouin(a)inlibro.com I have one plugin who have to know the biblionumber to add a custom button in the toolbar in the page details.pl But currently, the method is called without parameter so the plugin doesn't know in which biblionumber details page it adds the new button. The parameter allows to create custom with the biblionumber link to the button. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 46

[Bug 20172] New: Add a search bar in list tables
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '26

01 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20172 Bug ID: 20172 Summary: Add a search bar in list tables Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Hi, It would be nice to add a search bar fot the tables in the list's module like comme les autres tableaux qui sont diponibles dans les différents module de Koha. This search box will help us when we have a lot of records in a list. It would be useful. It could be a tables like on this page circ/overdue.pl. Patrick. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 41151] New: Vue Additional Fields UX Improvements
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '26

01 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41151 Bug ID: 41151 Summary: Vue Additional Fields UX Improvements Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The additional fields input UI's could do with some improvements as noted in bug 38262. To summarise: 1) Spacing between 'Clear' and 'New' buttons on input fields needs work 2) When viewing repeatable, searchable fields in display tables we use a comma separated list instead of field per line. 3) When viewing fields in details display the alignment of the addiional field labels and container is inconsistent I'd go further on point one and ask why we need 'Clear' as a distinct element as it's inconsistent with the 'normal' field entry input boxes. I think I'd prefer to try and make additional fields as consistent as possible with normal input fields, perhaps embedding a 'x' clear check within the far right of input fields to give that 'Clear' functionality accross both additional field and normal field inputs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 82

[Bug 35128] New: move cities to Vue
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '26

01 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35128 Bug ID: 35128 Summary: move cities to Vue Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.derscheid(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com This bug aims to be a reference point for migrating a traditional view, in this case admin/cities.pl to vue. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 30225] New: Rewrite cities admin view in Vue
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '26

01 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30225 Bug ID: 30225 Summary: Rewrite cities admin view in Vue Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Same as bug 30160 but using Vue 3 -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 13985] [Omnibus] Cash Management - Koha as 'Point of Sale'
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '26

01 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13985 Martin Renvoize (ashimema) <martin.renvoize(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |42959 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42959 [Bug 42959] Migrate staff interface functionality from CGI controller + Template Toolkit to REST API + Vue.js -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 38010] New: Migrate vendors to Vue
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '26

01 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38010 Bug ID: 38010 Summary: Migrate vendors to Vue 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: matt.blenkinsop(a)ptfs-europe.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 487

[Bug 40294] New: Mandatory patron expiration notice is not sent if patron does not have a primary contact method defined
by bugzilla-daemon＠bugs.koha-community.org 01 Jul '26

01 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40294 Bug ID: 40294 Summary: Mandatory patron expiration notice is not sent if patron does not have a primary contact method defined Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Depends on: 30301 Bug 30301 added the option to force mandatory account expiration notices for a given patron category in the membership_expiry cron. In these cases, the primary contact method on the patron account is used to determine the transport type for the notice. However, primary contact method may not be a mandatory field depending on the system preference settings. If a patron doesn't have a primary contact method set for their account, this causes the notice not to get sent at all, even if the patron has one or more valid email addresses or SMS number on their account. We need a fallback to ensure the mandatory notice is sent in this case. I think it would make the most sense to specify transport type(s) in the patron category settings when making account expiration notices mandatory for that category. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30301 [Bug 30301] Add an option to specify the patron expiration notices as mandatory by patron category -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 35