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

[Bug 19917] New: Holds for self registered patrons
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '25

17 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19917 Bug ID: 19917 Summary: Holds for self registered patrons Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 There needs to be a switch in place that does not allow a hold to be triggered if the hold is for a patron in the self registered category. Our library workflow: * Allows self registered patrons to place a couple of holds. * Doesn't assign an automatic card number. * Prints specialized hold slips * Allows self pickup Ideally, we would want the preference to not trigger the hold if the self registration category is in use on the patron with the hold, and a message to come up asking staff to go ahead and assign a card number, or something to that effect. Right now, when the hold is triggered, the slip comes out wrong because there is data missing. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 20575] New: Auto-renewals to use current patron category when renewing as opposed to when item was issued.
by bugzilla-daemon＠bugs.koha-community.org 17 Dec '25

17 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20575 Bug ID: 20575 Summary: Auto-renewals to use current patron category when renewing as opposed to when item was issued. Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Increasing the functionality of the Auto=-renewal process to have Koha look at the circulation and fine rule table at time of renewal instead of keeping the same circ and fine rules when the item was issued. If a patron category has been changed during when an item has been checked out the patron, this is not reflected in the auto-renewal process. For example, if a student is allowed to auto renewal items but they are changed to a different patron category who can not auto-renewal-Koha will still allow the auto-renewal given the rules were set when the item was checked out. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 20338] New: Preference noissuescharge should not be considered 5 when it is actually 0
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '25

09 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20338 Bug ID: 20338 Summary: Preference noissuescharge should not be considered 5 when it is actually 0 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When the noissuescharge is set to 0, then limit 5 is used, see FIXME comment in circ/circulation.pl after bug 19933 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 25219] New: Include note in fines-related system preferences which can be disabled by leaving them blank
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '25

09 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25219 Bug ID: 25219 Summary: Include note in fines-related system preferences which can be disabled by leaving them blank 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The syspref OPACFineNoRenewals includes the note "(leave blank to disable)." The sysprefs maxoutstanding, noissuescharge, NoIssuesChargeGuarantees, and MaxFine can all be disabled by leaving them blank, as well. It'd be helpful to include that same "(leave blank to disable)" message to make it clear. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 16291] New: koha-remove --purge should also delete /etc/koha/sites/instance
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '25

05 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16291 Bug ID: 16291 Summary: koha-remove --purge should also delete /etc/koha/sites/instance Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org It would be useful if 'koha-remove --purge' also deleted a /etc/koha/sites/instance dir -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 20508] New: Validation for *MandatoryField and *UnwantedField sysprefs
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '25

05 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20508 Bug ID: 20508 Summary: Validation for *MandatoryField and *UnwantedField sysprefs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When any the system preferences BorrowerMandatoryField BorrowerUnwantedField PatronSelfModificationBorrowerUnwantedField PatronSelfRegistrationBorrowerMandatoryField PatronSelfRegistrationBorrowerUnwantedField are being populated, we should check that a) The entered fields are columns in the borrowers table b) Mandatory / Unwanted fields that refer to the same form (BorrowerMandatoryField/BorrowerUnwantedField and PatronSelfRegistrationBorrowerMandatoryField/PatronSelfRegistrationBorrowerUnwantedField) do not contain the same fields. c) If autoMemberNum is set, don't allow cardnumber in *MandatoryField See also: * Bug 17433 * Bug 19642 * Bug 19225 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 22848] New: Ability to merge suggestions
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '25

05 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22848 Bug ID: 22848 Summary: Ability to merge suggestions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- It can easily happen that multiple suggestions for the same record are made. It would be nice if there was an option to merge them and keep both patrons who made the suggestion linked to it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 20271] New: Merge deleted/old tables with their "alive" cousins
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '25

03 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20271 Bug ID: 20271 Summary: Merge deleted/old tables with their "alive" cousins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P1 - high Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: boutrosboutrosboutros(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In Koha's DB, instead of having a "soft" deletion of entries by flagging the deleted one as so, the rows in the db is actually deleted, but only after a new row in a different table is inserted. Koha's DB is relational, so there is a cascade of links between each object: a biblio is referred by many items, and each item is referred by issues, holds, messages. E.g.: when a row in the item table is moved from "items" to "deleted_items", then all the references from holds, transfers and so on will be broken. The suggested more orthodox approach to this would be to add a "deleted_at" column, which is normally null unless the row is deleted, then it set to the timestamp of when it was deletion. This means that the row is still there and will still be referred by other tables, but it just won't be shown in the relevant lists. This would improve the maintenance of Koha in many ways (e.g.: the auto_increment id on those tables caused lots of issues when you add an item and delete it immediately after. the next new item will have the same itemnumber as the previously deleted one, clashing with it in many ways). This bug is about merging the all these tables: deletedborrowers => borrowers deletedbiblio => biblio deletedbiblioitems => biblioitems deletedbiblio_metadata => biblio_metadata deleteditems => items old_issues => issues old_reserves => reserves -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 383

[Bug 20269] New: Allow selecting default collate rule
by bugzilla-daemon＠bugs.koha-community.org 03 Dec '25

03 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20269 Bug ID: 20269 Summary: Allow selecting default collate rule 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: pasi.kallinen(a)joensuu.fi QA Contact: testopia(a)bugs.koha-community.org For some languages, the default collate rule set in kohastructure.sql, utf8_unicode_ci, doesn't work correctly. For example, Finnish alphabet expects the alphabet to sort abc...xyzåäö, but the unicode_ci rule doesn't handle the åäö right. Instead, we need to use the swedish_ci rule. It would be nice to be able to define the default collate rule during install. Problem can be seen for example when you go catalogue a new record and have frameworks starting with 'ä' or 'ö', those will sort incorrectly. On the database, you can test this with: insert into biblio_framework (frameworkcode, frameworktext) values ('TEST', 'Äänikirja'); -- Note where the 'Äänikirja' is located select * from biblio_framework order by frameworktext collate utf8_unicode_ci; -- And then the correct order, with 'Äänikirja' last: select * from biblio_framework order by frameworktext collate utf8_swedish_ci; -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 22330] New: Transfer limits should be respected for placing holds in staff interface and APIs
by bugzilla-daemon＠bugs.koha-community.org 27 Nov '25

27 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22330 Bug ID: 22330 Summary: Transfer limits should be respected for placing holds in staff interface and APIs Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- Branch transfer limits are respected for placing holds in the OPAC but nowhere else. This should be remedied. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 42