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

[Bug 41956] New: Hold group/hyperhold modals should show hold_group_id
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '26

31 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41956 Bug ID: 41956 Summary: Hold group/hyperhold modals should show hold_group_id Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: andrew(a)bywatersolutions.com, gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com It would be helpful if hyperholds' hold_group_id were more readily visible for staff who need to identify it in order to search logs/troubleshoot. Places it would help to have it visible: In the Holds tab of patron accounts in the staff interface (circulation.pl and moremember.pl), the modal generated by clicking on the number in the 'Hold group' column to see other titles/items in the hyperhold/hold group In a bib's hold tab (request.pl), the modal generated by clicking on the '(part of a hold group)' link in the hold's Details column -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 33430] New: Suggestions.pl with several hundred items causes a slow loading screen
by bugzilla-daemon＠bugs.koha-community.org 31 Jul '26

31 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33430 Bug ID: 33430 Summary: Suggestions.pl with several hundred items causes a slow loading screen Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The purchase suggestion management page take anywhere between 15-45 seconds to load if there are several hundred items in the suggestions table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 118

[Bug 41484] New: Wording of 'On hold', 'Booked', and 'Recalled' in issues table can be confusing
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '26

30 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41484 Bug ID: 41484 Summary: Wording of 'On hold', 'Booked', and 'Recalled' in issues table can be confusing Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the issues table there are columns for renew and check in that contain checkboxes. These are phrased as 'On hold', 'Booked', and 'Recalled'. This causes confusion for some as they can mistakenly think that item is On hold', 'Booked', or 'Recalled' for that patron. I propose using this for additional clarity: -Item on hold for another patron -Item booked for another patron -Item recalled by another patron -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 43207] New: Solve "Bug 41484 - Wording of 'On hold', 'Booked', and 'Recalled' in issues table can be confusing" differently?
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '26

30 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43207 Bug ID: 43207 Summary: Solve "Bug 41484 - Wording of 'On hold', 'Booked', and 'Recalled' in issues table can be confusing" differently? Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Depends on: 41484 Target Milestone: --- Opening a new bug for better visibility and for discussion. We noticed that the descriptions for "On hold" "Booked" and "Recalled" have been updaed to much longer descriptions, which take up more space in the table and can make it look more cluttered. Baptiste also commented: (In reply to Katrin Fischer from comment #10) > The new wordings are really long and repeated in 2 columns of the table, > they get even longer when translated to German. I am not sure if this is > overall an improvement. > > Maybe we could have a short wording and a longer one on hover? > > Space in circulation is always valuable. (In reply to Baptiste Wojtkowski (bwoj) from comment #12) > Following up Comment 10, some customer also reported they felt less > comfortable with the new wording I feel like a shorter text with a longer tooltip might be a good middle ground here? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41484 [Bug 41484] Wording of 'On hold', 'Booked', and 'Recalled' in issues table can be confusing -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 41917] New: Parent itemtype fallback missing for bookable flag and circulation rules
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '26

30 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41917 Bug ID: 41917 Summary: Parent itemtype fallback missing for bookable flag and circulation rules Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: paul.derscheid(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com When item types are organized in a parent-child hierarchy, child item types do not inherit settings from their parent. This means that every child item type needs its own bookable flag and its own set of circulation rules, even when the parent already defines them. The expected lookup order should be: 1. Item-level / child itemtype-specific value 2. Parent itemtype value 3. Global default Currently step 2 is skipped entirely, so the system jumps straight from a missing child-specific value to the global default. This affects Item::effective_bookable, Items::filter_by_bookable, and CirculationRules::get_effective_rule. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[Bug 43200] New: Prevent Bookable item types from being deleted if there are still bookings for it to fill.
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '26

30 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43200 Bug ID: 43200 Summary: Prevent Bookable item types from being deleted if there are still bookings for it to fill. Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: LIrwin(a)jcls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- We recently discovered that if the bookable item associated with a booking is deleted the booking gets unexpectedly deleted from the database as well. During testing I also discovered that if all bookable items on a bib are deleted the bookings on the bib record also get erased from the database as well even if the bookings aren't specifically associated with one of the bookable items on the bib record. The problem with this is that frontline staff won't know that this has occurred until the patron comes in wanting to know what happened to their booking. When this issue came up for our library system, I couldn't find the booking that disappeared with I used a sql report to see all the data stored in the bookings' table. The only evidence I had that that this booking had existed in the first place came from past reports that we had letting front line staff know that there was a booking coming up that they would need to send out to be picked up soon. For now, the only workaround I can think of is to manually check our bookable bib records for active bookings before withdrawing and deleting those records. It would be helpful if Koha prevented bookable items from being deleted after withdrawing them if there were active bookings still on the record. This would help prevent staff from accidentally deleting a booking as a result of deleting a bookable item. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 42642] New: Move background report jobs to a dedicated queue
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '26

30 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42642 Bug ID: 42642 Summary: Move background report jobs to a dedicated queue Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com Background report jobs from bug 41921 are run in the long_tasks queue. For greater control ( and to not back up other long_tasks jobs ) it would make sense to put them in a dedicated queue. This would allow the library to control how many reports can be run simultaneously on a given instance. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 39917] New: Display a prompt for status alias when completing a request
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '26

30 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39917 Bug ID: 39917 Summary: Display a prompt for status alias when completing a request Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: pedro.amorim(a)openfifth.co.uk Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 38819] New: ILL - 'Switch provider' should use AutoILLBackendPriority
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '26

30 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38819 Bug ID: 38819 Summary: ILL - 'Switch provider' should use AutoILLBackendPriority Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: pedro.amorim(a)ptfs-europe.com Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: andrew.auld(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com Depends on: 38669 Currently, the 'Switch provider' option lists all other installed backends and forces the user to pick one. If AutoILLBackendPriority is enabled, this action should make use of it, i.e. present the automatic backend screen, query all installed backends for availability and suggest the most appropriate one. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38669 [Bug 38669] ILL - Staff: Automatic backend screen should provide option to go back to form -- You are receiving this mail because: You are watching all bug changes.

1 77

[Bug 38669] New: ILL - Staff: Automatic backend screen should provide option to go back to form
by bugzilla-daemon＠bugs.koha-community.org 30 Jul '26

30 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38669 Bug ID: 38669 Summary: ILL - Staff: Automatic backend screen should provide option to go back to form Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: pedro.amorim(a)ptfs-europe.com Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com Depends on: 35604 On the automatic backend screen, each backend may provide different reasons to why the availability check has failed, and sometimes this can be "fixed" by updating the form metadata. Because of this, there should be the possibility of going back to the form from this screen. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35604 [Bug 35604] ILL - Allow for automatic backend selection -- You are receiving this mail because: You are watching all bug changes.

1 34