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

[Bug 37248] New: [Omnibus] Power to the user
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37248 Bug ID: 37248 Summary: [Omnibus] Power to the user 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: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This is for the initiative for helping to ensure that users can do as much of the configuration in the interface rather than the command line. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 20153] New: Add new column "source" in the authorities pages's result
by bugzilla-daemon＠bugs.koha-community.org 16 Mar '26

16 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20153 Bug ID: 20153 Summary: Add new column "source" in the authorities pages's result Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging 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 if we could add a new column in the results page of a search in authority's module.In this new column we could se the subfield 040 $a who show the Organization that performed the original cataloging. With this new column with this new column titled "source", like the column in the z39.50 search, we would not need to go back to the authority record to see if it's a locally created authority or if it's imported. Patrick. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 36136] New: Flatpickr allows selecting date from the past on copied serial subscriptions
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '26

14 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36136 Bug ID: 36136 Summary: Flatpickr allows selecting date from the past on copied serial subscriptions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org If a librarian copies a serial subscription and changes dates the Flatpickr allows to put end date to the past. Flatpickr prevents the action only if the start date is first added. In this case the old input value should be passed to the Flatpickr so the selection is not allowed. I think this happens everywhere where we are using Flatpickr. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 29768] New: hidepatronname hides guarantor name on borrower edit screen
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '26

14 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29768 Bug ID: 29768 Summary: hidepatronname hides guarantor name on borrower edit screen Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: bdaeuber(a)cityoffargo.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The syspref hidepatronname is now hiding the guarantor name on memberentry.pl. This seems like a strange place to enforce that system preference since it's convenient for staff to be able to double check that info when editing patron information and personal information is already showing on that screen. It's not enforced on other patron details screens (such as moremember.pl) and I don't think it should impact patron edit screen either. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 48

[Bug 28308] New: Select 'Days in advance' = 0 for Advance notice effectively disables PREDUE notices
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '26

14 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28308 Bug ID: 28308 Summary: Select 'Days in advance' = 0 for Advance notice effectively disables PREDUE notices Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Looking at the code below, it seems that on the day an item is due we will only send the DUE notices, predues will not be sent In the advance_notices.pl cron: 276 if ( 0 == $upcoming->{'days_until_due'} ) { 277 # This item is due today. Send an 'item due' message. ... 323 } else { 324 $borrower_preferences = C4::Members::Messaging::GetMessagingPreferences( { borrowernumber => $upcoming->{'borrowernumber'}, 325 message_name => 'advance_notice' } ); 326 next UPCOMINGITEM unless $borrower_preferences && exists $borrower_preferences->{'days_in_advance'}; 327 next UPCOMINGITEM unless $borrower_preferences->{'days_in_advance'} == $upcoming->{'days_until_due'}; In this case, allowing the user to choose '0' is effectively disabling the notice. I think we need to remove 0 as an option, and uncheck all transports for patrons who have '0' set for days in advance -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 31550] New: WS ILSDI opac description for some item fields
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '26

14 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31550 Bug ID: 31550 Summary: WS ILSDI opac description for some item fields Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org It may be useful to get the opac description on the ILSDI web service with a specific suffix for some item fields. In relation to bug 25650, this is to add 'ccode', 'permanent_location', 'notforloan', 'itemlost', 'withdrawn', 'damaged' and 'restricted'. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 38139] New: Refactor C4::Auth::getuserflags() and move to Koha::Auth::Permissions->get_flags() with unit tests
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '26

13 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38139 Bug ID: 38139 Summary: Refactor C4::Auth::getuserflags() and move to Koha::Auth::Permissions->get_flags() with unit tests 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: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Breaking the concerns from Bug 20813 - Revamp user permissions system into smaller pieces. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 38141] New: Move "flags" column into "user_permissions" table
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '26

13 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38141 Bug ID: 38141 Summary: Move "flags" column into "user_permissions" table 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: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Breaking the concerns from Bug 20813 - Revamp user permissions system into smaller pieces. (that said, this could have unexpected consequences for borrower_modifications and deletedborrowers...)(this also will have consequences with manual SQL and tests) The goal of the above is to free us from the bit-packed "flags" integer and separate sub-permission table, so that it's easier to create and organise flags/permissions. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 38140] New: pdate Acquisition.pm, Budgets.pm, about.pl, and other users of authorization data checks outside of the initial AuthZ check on page load
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '26

13 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38140 Bug ID: 38140 Summary: pdate Acquisition.pm, Budgets.pm, about.pl, and other users of authorization data checks outside of the initial AuthZ check on page load 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: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Breaking the concerns from Bug 20813 - Revamp user permissions system into smaller pieces. The goal of the above is to centralize the business logic of permission/authorization checks in Koha, so we're not repeating complex code structures throughout the app. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 38063] New: Add batch patron permission modification
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '26

13 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38063 Bug ID: 38063 Summary: Add batch patron permission modification 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: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org We have a plugin for batch permission modification: https://github.com/bywatersolutions/koha-plugin-batch-permissions-modifier I think it would be beneficial to move this into core as a way to do a mix of role-based access control and per-user permissions. How the plugin works 1. Set permissions of a template user 2. Create a patron list of all the users who should have those permissions 3. In the plugin, assign the template user to the list 4. User's permissions are now controlled by the template user. Permissions can only be changed on the template user. Users who aren't assigned to a role list can have their permissions edited as it currently works. Currently only one role is allowed at a time. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5