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

[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 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 29497] New: Add ability to link authorities automatically in the advanced editor
by bugzilla-daemon＠bugs.koha-community.org 30 Mar '26

30 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29497 Bug ID: 29497 Summary: Add ability to link authorities automatically in the advanced editor Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: estherm(a)sodaspringsid.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be nice to add the link authorities automatically button in the advanced editor. Right now catalogers must use the basic editor in order to use this option. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 20958] New: Allow admins to choose data types for additional attributes
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '26

28 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20958 Bug ID: 20958 Summary: Allow admins to choose data types for additional attributes 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: hughr(a)brimbank.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently additional patron attributes are always strings. It would be really useful to be able to specify what data type an additional attribute should be when it is created, like you can specify whether it has to be unique, or is repeatable. e.g. we might want it to be a DATE, or possibly a DATETIME, or we may indeed want a STRING, or an INT, or a DECIMAL etc - it really depends on what a given library is using the attributes for, and how they might want to run reports against it. This would be a more holistic way to deal with Bug 6339. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 19336] New: Add option to fines.pl to apply maximal fine amount after delay
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '26

28 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19336 Bug ID: 19336 Summary: Add option to fines.pl to apply maximal fine amount after delay Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.bourgault(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 88

[Bug 20682] New: Authorised values should have an option to set a default
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '26

27 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20682 Bug ID: 20682 Summary: Authorised values should have an option to set a default Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: hughr(a)brimbank.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are many places in Koha where values can be chosen via a drop-down menu listing a particular authorised value. For example SUGGEST_FORMAT is used to populate the list of formats that can be selected when placing a purchase suggestion. Currently these lists appear in alphabetical order by description or OPAC description (depending on context), and the first option in the list is usually auto-selected (i.e. more or less default behaviour for a vanilla HTML <select> element). This is problematic in many circumstances as users will accidentally 'select' the first alphabetical option if they don't change anything. There should be a setting in Authorised Values to set between zero and one values per category to be the default value (probably in authorised_values.pl?op=add_form). This would then add a 'selected' attribute to the <option> tag wherever the authorised value list appears as a dropdown menu. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 30047] New: Add a field to auth_header to record main heading as text string
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '26

27 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30047 Bug ID: 30047 Summary: Add a field to auth_header to record main heading as text string Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org SQL queries looking at authority records are complicated by the fact that authorities don't have an equivalent to a biblio's title. It would be helpful to create a new database field (auth_header.main_heading) in which we record a text string. The specific value we record here would be determined by the authority type, following the mappings defined in authtypes.pl. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 37

[Bug 26342] New: Suspended hold not marked filled when patron checks out item
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '26

26 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26342 Bug ID: 26342 Summary: Suspended hold not marked filled when patron checks out item Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: - place an item-level hold - suspend the hold - without unsuspending or capturing the hold, check the item out to the patron - the suspended hold remains on the patron account If a hold is not suspended (and not captured) and the patron checks the item out, the hold is marked as filled. Should we do the same on suspended holds? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 30221] New: Make the tables on opac-user.tt column configurable
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '26

26 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30221 Bug ID: 30221 Summary: Make the tables on opac-user.tt column configurable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org There are several tables on opac-user.tt that would benefit from being column configurable. ( check-outs, overdues, charges, holds, article requests ) -- You are receiving this mail because: You are watching all bug changes.

1 99

[Bug 20784] New: Capture more changes in Logs
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '26

26 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20784 Bug ID: 20784 Summary: Capture more changes in Logs Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice to have an Administration Log. A log that tracks changes (add/modify/deletes) to branch information, itemtype information, circ rules, authorised_values (others areas). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9