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

[Bug 38407] New: Eliminate event handler attributes in the staff interface
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '26

25 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38407 Bug ID: 38407 Summary: Eliminate event handler attributes in the staff interface Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Like bug 34709 but for the staff interface -- You are receiving this mail because: You are watching all bug changes.

1 40

[Bug 39959] New: Ability to customize the invoice table
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '26

25 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39959 Bug ID: 39959 Summary: Ability to customize the invoice table Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: hdunne-howrie(a)westminster.gov.uk QA Contact: testopia(a)bugs.koha-community.org We want to be able to customize the invoice tables we see here https://wcc-rbkc-staff.koha-ptfs.co.uk/cgi-bin/koha/acqui/invoices.pl like we can for the order tables so we can add in the columns we want or hide columns as needed. In particular, we want to be able to add in total columns to this view so when we search for invoices we see the total amounts in the search results to quickly help us work out which invoice is which when we have limited information but know the total amount. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 39337] New: Use SQL field to apply OpacSuppression in OAI-PMH
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '26

25 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39337 Bug ID: 39337 Summary: Use SQL field to apply OpacSuppression in OAI-PMH Change sponsored?: --- Product: Koha Version: unspecified 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 37713, 38330 This is a follow-up to bug 37713 and bug 38330. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37713 [Bug 37713] OAI-PMH - Honour OpacSuppression syspref https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38330 [Bug 38330] Make bib-level suppression a biblio table field instead of part of a marc tag -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 38

[Bug 38647] New: Can't filter holdings table by shelving location
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '26

25 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38647 Bug ID: 38647 Summary: Can't filter holdings table by shelving location Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In 24.05, libraries can no longer filter the holdings table in the staff interface by shelving location since the Home library column is now a drop-down instead of allowing free text entry. As of 23.11, the filtering was free text instead of a drop-down, which meant that libraries could type a library name *or* a shelving location to filter. Additionally, the holdings table search bar doesn't appear to 'read' shelving locations, so libraries can't use that to pinpoint items with a specific shelving location either. This will likely be moot with Bug 15461 - Add staff equivalent for OpacLocationOnDetail, but in the meantime, it isn't user-friendly for libraries who need that column to filter bibs with many holdings. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 34164] New: OAuth2/OIDC should redirect to page that initiated login
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '26

25 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34164 Bug ID: 34164 Summary: OAuth2/OIDC should redirect to page that initiated login 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org At the moment, a successful OAuth2/OIDC login is sent to opac-user.pl/opac-main.pl or mainpage.pl instead of the page that initiated the login process. With Shibboleth, we manage this using the "target" URL, so that the Shibboleth login is processed by whatever page initiated it, but that doesn't work with OAuth2/OIDC and the "redirect_uri" since we're using an API endpoint. However, all we need to do is save the current path in the user's session, and then recall it after the successful login. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44

[Bug 29948] New: Display author information for researches
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29948 Bug ID: 29948 Summary: Display author information for researches Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: OPAC Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 29897 Display author's information from 371, 372, 373 (email, activity, etc.) in the same area than identifiers (from bug 29897). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29897 [Bug 29897] Display author identifiers for researchers -- You are receiving this mail because: You are watching all bug changes.

1 68

[Bug 26573] New: Limit patron attribute types to more than one patron category
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26573 Bug ID: 26573 Summary: Limit patron attribute types to more than one patron category Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration 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 Currently, Koha doesn't allow to limit a patron attribute type to more than one patron category. Let's say I have a patron attribute type STUDENTID, and I want to limit this attribute to the categories "undergrad students" and "grad students". I have to create two different patron attribute types. To replicate: 1) Go to Administration > Patron attribute types 2) Create a new patron attribute 3) Note that the "Category" field is a dropdown and you can't choose more than one patron category to assign this attribute type to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 93

[Bug 26197] New: Using Rancor while cataloging doesn't appear to check for existing records
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26197 Bug ID: 26197 Summary: Using Rancor while cataloging doesn't appear to check for existing records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Upon testing this, while cataloging a new record using the basic editor Koha will find a duplicate record existing in Koha but didn't find the same duplicate using the Advanced Editor. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 39885] New: There should be a default notice to send to patrons when a new suggestion has been created by them or for them
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39885 Bug ID: 39885 Summary: There should be a default notice to send to patrons when a new suggestion has been created by them or for them Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org There should be a default notice ( maybe ASKED? ) that will optionally be sent when a new suggestion is created by a patron ( OPAC ) or on behalf of a patron ( staff interface ). This is not to be confused with NEW_SUGGESTION, which is sent to staff when a new suggestion is created. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 38255] New: Do not use dataTable constructor directly
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '26

24 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38255 Bug ID: 38255 Summary: Do not use dataTable constructor directly Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 36640 We should not use dataTable() but our own KohaTable or kohaTable. It will help to get rid of repeated rules (eg. NoSort). Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36640 [Bug 36640] Upgrade DataTables from 1.13.6 to 2.x -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 132