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

[Bug 37444] New: Can't filter Holds to pull by Pickup Location
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '25

09 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37444 Bug ID: 37444 Summary: Can't filter Holds to pull by Pickup Location Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: stalkernoid(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 30800] New: Ability to view, modify, and delete profiles for staging MARC records for import
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '25

08 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30800 Bug ID: 30800 Summary: Ability to view, modify, and delete profiles for staging MARC records for import Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be useful to have a place to view/edit all profiles that a library has created for use while staging MARC records for import in one place - maybe similar to 'Manage MARC modification templates'. It could include each profile's settings and the ability to delete individual/multiple at a time, and if possible, the ability to add new, edit existing, and/or duplicate to create new. But at a minimum, being able to see what exists and delete from there rather than the 'Stage MARC records for import' screen would be helpful. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31281] New: Overdue notices reply-to email address of a branch not respected
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '25

06 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31281 Bug ID: 31281 Summary: Overdue notices reply-to email address of a branch not respected Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nason.bimbe(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org The overdue notification email is sent from the correct email address as set up for the branch, however the reply-to email address though set for the branch is not the one used. The email has reply-to address of a different branch and not even the default one as set up in system preferences. Below is set up (however I have renamed the branches and email addresses for the purpose of this bug report). So what happened is the overdue notification was sent using LibraryB email address however the reply-to email address on the notification is the reply-to email address of LibraryA instead of LibraryB one. This is on Koha 21.11.05.000 LibraryA settings Email: librarya(a)mlibary.whatever Reply-To: librarya(a)mlibrary.whatever Return-Path: librarya(a)mlibrary.whatever LibraryA settings Email: libraryb(a)mlibary.whatever Reply-To: libraryb(a)mlibrary.whatever Return-Path: libraryb(a)mlibrary.whatever LibraryC settings Email: libraryc(a)mlibary.whatever Reply-To: libraryc(a)mlibrary.whatever Return-Path: libraryc(a)mlibrary.whatever SysPref setting: KohaAdminEmailAddress: library(a)library.whatever ReplytoDefault: library(a)library.whatever -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 35646] New: Allow using the publication date parts for serial numbering
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '25

05 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35646 Bug ID: 35646 Summary: Allow using the publication date parts for serial numbering 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Sometimes libraries want date fields based on publication date included in the numbering, say for a weekly serial -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 38

[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 33473] New: Allow to send email receipts for payments/writeoff manually instead of automatically
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '25

05 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33473 Bug ID: 33473 Summary: Allow to send email receipts for payments/writeoff manually instead of automatically Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 31448 With bug 31448 it's possible to re-send a failed or lost email receipt. It would be nice if you could turn off the automatic sending of receipts by email and send them just manually whenever requested. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31448 [Bug 31448] Add option to re-send email receipt when UseEmailReceipts is enabled -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 29140] New: Suppress some warnings in codemirror js editor
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '25

05 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29140 Bug ID: 29140 Summary: Suppress some warnings in codemirror js editor 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When editing user JS preferences there are warns for: 'let' is available in ES6 I think we could suppress these and allow that usage -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[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 34295] New: Staff-only extended attributes break self-registration
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '25

05 Dec '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34295 Bug ID: 34295 Summary: Staff-only extended attributes break self-registration Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: JBoyer(a)equinoxOLI.org QA Contact: testopia(a)bugs.koha-community.org If any patron extended attributes are defined that are mandatory and not opac-editable (such as Address Verified: Yes / No) patron self-registration will always return a 500 error because the mandatory attribute is not / can not be supplied. Avoiding this by limiting mandatory attributes to a specific patron category fails as soon as you want to apply an attribute to 2 or more categories. -- You are receiving this mail because: You are watching all bug changes.

1 4