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

[Bug 15522] New interface for revamped circulation rules
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '26

01 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15522 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=39127 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 33965] New: Hide patron accounts that are for admin use only
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '26

01 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33965 Bug ID: 33965 Summary: Hide patron accounts that are for admin use only Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We should have a setting that only superlibrarians can set to hide patron accounts that regular staff should not need to alter. Test accounts, anonymous patron accounts, etc. Superlibrarians would be the only users that could alter accounts marked as such. You should not be able to mark superlibrarian accounts as hidden. Regular staff would be able to see names and card info throughout the system, but they would not be able to view the patron record. They should be shown a screen like "Admin use only." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 42227] New: Missing suggestions_delete or suggestions_manage permissions can cause a table error when viewing purchase suggestions
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '26

31 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42227 Bug ID: 42227 Summary: Missing suggestions_delete or suggestions_manage permissions can cause a table error when viewing purchase suggestions Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: michael.adamyk(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 196611 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=196611&action=e… Image of error If a staff member doesn't have full suggestions permissions, Koha is sometimes giving a Javascript error that reads "Something went wrong when loading the table. 200: Success." However, it's very difficult to track down which permission it actually is. I have encountered the problem when removing either suggestions_delete, suggestions_manage, or both. However, sometimes it seems like only missing one will trigger the error, other times it needs to be missing both preferences. It seems that regardless of which preference, missing at least some suggestions permissions are causing this table load error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 30795] New: Configure unwanted and mandatory borrower fields based on patron category
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '26

31 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30795 Bug ID: 30795 Summary: Configure unwanted and mandatory borrower fields based on patron category Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice if there were a way to specify different unwanted and mandatory fields based on patron category (rather than enforcing 1 rule for all different patron categories). At the moment, I see libraries putting in junk data (like '-' or 'N/A') to get around mandatory field requirements where it doesn't make sense for certain patron categories. It makes sense to have a default rule for these fields, and then individual patron categories could be overwritten with more specific rules. -- I suppose the difficulty at the moment is that we don't choose a patron category until we're already on the add patron screen. Maybe we should be making it a multi-step process. That would have its pros and cons of course. Actually, this reminds me of another thought I've had where we could standardize CRUD forms... but I'll open another bug for that... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 42223] New: Patron category privacy setting not respected when changing category
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '26

31 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42223 Bug ID: 42223 Summary: Patron category privacy setting not respected when changing category Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com If you have one patron category with the Privacy setting set to e.g. "Default" and use this to create a new user, the borrowers.privacy setting is set to 1. If you then edit this user to have a category that has a privacy setting of "Forever", the borrowers.privacy setting doesn't get updated to 0 and the only way to change this is to delete the user and recreate. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 37428] New: Improve the AllowItemsOnHoldCheckoutSIP system preference description
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '26

31 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37428 Bug ID: 37428 Summary: Improve the AllowItemsOnHoldCheckoutSIP system preference description Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org The AllowItemsOnHoldCheckoutSIP system preference description is confusing and could be updated to make it clearer and easier to understand. Current description: [Don't allow/Allow] checkouts of items reserved to someone else via SIP checkout messages. If allowed do not generate RESERVED warning. This allows self checkouts for those items. If using the holds queue items with pending holds will be marked as "unavailable" if this set to "Don't allow". Discussed on chat: - General discussion: https://chat.koha-community.org/koha-community/pl/81zs86ckd7rypp94qnt7s9cu9e - Explanation: https://chat.koha-community.org/koha-community/pl/yjrkugm99bgxdxy7h4snk6qyee -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 34162] New: Customize required patron registration fields by patron type
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '26

31 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34162 Bug ID: 34162 Summary: Customize required patron registration fields by patron type Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kkrueger(a)cuyahogalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries have different required fields by patron type. For example, regular borrowers may be required to have a birth date, but an Institution patron type would not have a birth date to enter in this field. It would be great to be able to customize the borrowermandatoryfield system preferences according to patron type. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 40524] Stored XSS run by DataTables Print button in staff interface
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '26

31 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40524 Fridolin Somers <fridolin.somers(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |42224 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 20582] New: Turn Koha into a Mojolicious application (?)
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '26

31 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20582 Bug ID: 20582 Summary: Turn Koha into a Mojolicious application (?) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 158

[Bug 42113] New: Add ability to enable/disable bundles
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42113 Bug ID: 42113 Summary: Add ability to enable/disable bundles Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: alyssa.drake(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org For libraries that do not use bundles, it would be helpful to have the option to disable or enable the ability of Koha to read the leader to create a bundle even if the collection indicator exists. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1