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

[Bug 26170] New: Create "system" patrons that cannot be (easily) deleted via the web ui
by bugzilla-daemon＠bugs.koha-community.org 16 Apr '25

16 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26170 Bug ID: 26170 Summary: Create "system" patrons that cannot be (easily) deleted via the web ui 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com At the moment, the only way to create OAuth2 or Basic Auth credentials is to generate a user. This user can be deleted by a librarian by accident, which will break your API integration with Koha. I propose that we make some system users that cannot be deleted from the Web UI. (Or users that can be deleted by a superlibrarian, but need to be "unlocked" first or maybe have their category changed, and a warning splashed that this will likely break integrations with other systems.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 78

[Bug 17815] New: Problems with search for dateaccessioned
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '25

14 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17815 Bug ID: 17815 Summary: Problems with search for dateaccessioned Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Tested this as described in bug 14861: Search from advanced search by accession date: 2011-09-01 - 2011-09-30 9461 results Searched with SQL: select distinct biblionumber from items where dateaccessioned between '2011-09-01' and '2011-09-30' 805 results The date range search doesn't seem to work right. The search for a single date appears to work correctly. It's also possible to truncate dates using *. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 23732] New: Hold rules checker: show matched rules and syspref values to help understand why a hold is possible or not
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '25

10 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23732 Bug ID: 23732 Summary: Hold rules checker: show matched rules and syspref values to help understand why a hold is possible or not Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 57

[Bug 23780] New: Batch check out fails to inform or trap
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '25

03 Apr '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23780 Bug ID: 23780 Summary: Batch check out fails to inform or trap Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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 I have managed to catch failures in Batch check out on the following scenario: Patron has fines over the allowed limit. Item type only allows 5 check outs. When checking out 6 of this item type, Batch check out failed to: * Show any information that the patron had reached fine limit * Show that the patron was checking out too many of this item type If I checked out these 6 items without the fine, it gives the warning about too many items and asks me to confirm. If I check out 5 of these items with the fine, it does not explain why I need to confirm. It seems that Batch check out: * Is not displaying a reason for confirmation with the fine block. * Is not displaying a reason for confirmation when there are multiple blocks. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 16275] New: Prevent patron creation if the email already filled in borrowers.email
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '25

31 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16275 Bug ID: 16275 Summary: Prevent patron creation if the email already filled in borrowers.email Change sponsored?: 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: nicolas.legrand(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some of our patrons are not sure they succeed their self registration and self register multiple times. We would like to prevent this by blocking the selfregistration if the field borrowers.email is already filled by the same email address. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25

[Bug 19366] New: PatronSelfRegistrationEmailMustBeUnique pref makes it impossible to submit updates via OPAC
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '25

31 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19366 Bug ID: 19366 Summary: PatronSelfRegistrationEmailMustBeUnique pref makes it impossible to submit updates via OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 16275 With PatronSelfRegistrationEmailMustBeUnique set to "Consider" I am unable to submit a change to my patron record via the OPAC because Koha performs the existing-email check on the email in the existing record I'm modifying. PatronSelfRegistrationEmailMustBeUnique should only apply new registrations. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16275 [Bug 16275] Prevent patron self registration if the email already filled in borrowers.email -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 18705] New: collections_tracking-table is missing index/ foreign key to items
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '25

31 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18705 Bug ID: 18705 Summary: collections_tracking-table is missing index/foreign key to items Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com This makes searches such as circ/pendingreserves.pl rather slow and very noticeable on HDDs -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 25781] New: Remove duplicate days_forward method from Koha::Calendar
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '25

31 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25781 Bug ID: 25781 Summary: Remove duplicate days_forward method from Koha::Calendar Change sponsored?: --- Product: Koha Version: master 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org With bug 15260 the 'next_open_days' method learnt to accept an integer number of days to add before calculating the next open day date. This, in effect, removes the requirement for the days_forward method that does the same. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 25295] New: Allow customization of staff client based on login location
by bugzilla-daemon＠bugs.koha-community.org 31 Mar '25

31 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25295 Bug ID: 25295 Summary: Allow customization of staff client based on login location Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With more library systems or multiple-branch libraries using Koha, it would be really helpful to be able to customize the look of the staff client based on the library a staff member is logged in at. For instance, allow a library system to designate a header or background color on the staff client based on the branch. So branch A would be green, branch B would be purple, etc. This would allow users to easily and quickly identify which branch they are logged in to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 26275] New: Deleting item should not automatically delete volume
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '25

28 Mar '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26275 Bug ID: 26275 Summary: Deleting item should not automatically delete volume Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: - create a bib - add an item - create a volume - add item to volume - in the Holdings table on detail.pl, check the box to select your item and pick Delete selected items - on the next page, do not check "Delete records if no items remain" - click Delete selected items - return to your bib. the item and volume are both gone I don't think we should automatically delete the volume when removing the last item. I'd like to see another check box on the batch deletion screen -- "delete volumes if no items remain" to parallel "delete records if no items remain" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6