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

[Bug 29002] New: Add ability to book items ahead of time
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29002 Bug ID: 29002 Summary: Add ability to book items ahead of time 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Normal loans allow a patron to pick an item and take it out immediately. Reserves allow a patron to add themselves to a queue for the item should it already be checked out to someone. We have a library that wishes to allow patrons to book items for a specific date and loan period and have the item guaranteed to be available to them for that period. This bug intends to introduce that functionality, adding a bookable option to items and exposing a calendar with bookable loan slots. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 232

[Bug 31998] New: Overdue print notice cron issue (owning library vs issuing library)
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31998 Bug ID: 31998 Summary: Overdue print notice cron issue (owning library vs issuing library) Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: laura(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Overdue notices are currently sent to the patron’s home library, not the owning or issuing library. The problem is the letter template used is based on either the owning or the issuing library (based on the cronjob option --frombranch). That means if a Library A patron has an overdue checked out/owned by Library B, then Library A will receive a print notice formatted with Library B’s template. To resolve this we can do one of two things: A) Add an option to format the notice using the template from the patron’s home library B) Add an option to send notices for print to the patron’s home library, but to the owning/checkout library (A) is a simpler solution, though (B) may be wanted by library systems that are more “independent” and don’t want to mail notices for overdues at other libraries. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 28857] New: Allow hold to be suspended at point of creation
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28857 Bug ID: 28857 Summary: Allow hold to be suspended at point of creation 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Holds with a future start date and an element of complexity that some libraries would like to avoid. Instead, they use suspensions to delay the fulfilling of holds. However, there's no way to suspend a hold as you place it -- you need to place the hold and then suspend it from another screen. We should make it possible to set a suspension on a hold as you place it. But we should make is easy to hide the option to do so, so this probably means a new system preference, something like SuspendHoldsAtCreation, with options for No / Intranet / OPAC / Both Intranet and OPAC. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 22459] New: Shibboleth create/sync: Allow mapping of extended patron attributes
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22459 Bug ID: 22459 Summary: Shibboleth create/sync: Allow mapping of extended patron attributes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Depends on: 18507 Target Milestone: --- It woudl be great if extended patron attributes could be mapped for provisioning with Shibboleth as well. One use case would be a unique key, that is also used/neded for patron imports and stored in an unique extended patron attribute. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18507 [Bug 18507] Shibboleth auto-provisioning - Sync -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 38519] New: Improve contrast of Bootstrap alerts and text background classes
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38519 Bug ID: 38519 Summary: Improve contrast of Bootstrap alerts and text background classes Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 35402 Created attachment 174934 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=174934&action=e… Screenshot showing examples of Bootstrap alerts and text with background Some of the built-in Bootstrap alert and text background classes aren't working very well in terms of visibility and contrast. The "info" alert should stand out more, and the text background classes don't all have usable contrast. See the attached screenshot. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 [Bug 35402] Update the OPAC and staff interface to Bootstrap 5 -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 38679] New: GET /deleted/biblios missing some mappings
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38679 Bug ID: 38679 Summary: GET /deleted/biblios missing some mappings Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com When we implemented the `GET /deleted/biblios` endpoint, we missing the mapping for the `biblioitems` table attributes. To reproduce: 1. Pick a sample record ID 2. Fetch is using the API with your favourite tool: GET /api/v1/biblios/<the ID> Accept: application/json 3. Save the output for later 4. Delete the record 5. Fetch the deleted biblio using the API: GET /api/v1/deleted/biblios/<the ID> Accept: application/json 6. Compare the results => FAIL: Attributes like `volumedate` are not mapped! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 38735] New: New installations should include preferred_name in DefaultPatronSearchFields by default
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38735 Bug ID: 38735 Summary: New installations should include preferred_name in DefaultPatronSearchFields by default Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: emily.lamancusa(a)montgomerycountymd.gov Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 28633 In bug 28633, preferred_name was added to DefaultPatronSearchFields if the preference already included firstname in the selected values. This should be the case for new installations as well. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 [Bug 28633] Add a preferred name field to patrons -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 38667] New: Point of sale transaction history should not appear to be sortable
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38667 Bug ID: 38667 Summary: Point of sale transaction history should not appear to be sortable Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Point of Sale Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)ptfs-europe.com The configurations of the Transactions to date and Older transactions tables contain "orderFixed: [ 0, 'asc']" which sets a fixed order on the hidden first column. We should add "ordering: false" so that column sorting controls don't appear in the table headers. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 38462] New: Remove unused code for pagination in OPAC authority search
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38462 Bug ID: 38462 Summary: Remove unused code for pagination in OPAC authority search Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: phil(a)chetcolibrary.org Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org The remote branch for bug 13618 started out when OPAC authority search did its own pagination in a template block, then bug 2735 replaced that with pagination_bar, the template var passed from the script, then at some point before bug 13618 landed the second time, a rebase error put the template block back in. And since it's not at all obvious it is dead code unless you look for where "pagination" rather than "pagination_bar" is used, we've kept updating it, and bug 36032 thought the way it used >> instead of > for next ought to be fixed while one that was actually used was fixed. Time to get rid of it, before we 'fix' it again. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 38302] New: Inconsistent Delete Confirmation Dialog for "Delete List" Buttons
by bugzilla-daemon＠bugs.koha-community.org 24 Feb '26

24 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38302 Bug ID: 38302 Summary: Inconsistent Delete Confirmation Dialog for "Delete List" Buttons Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: yanjun.li(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In the staff interface, there're two ways to delete a list: 1) "Delete" button in "Your lists" table 2) "Delete List" button in "Edit" dropdown Option 2) has a confirmation dialog "Are you sure you want to delete this list?" but option 1) does not. To recreate: 1. Create a list in the staff interface 2. Go to lists 3. See "Your lists" tab and find "Delete" button in "Actions" col, click "delete", no confirmation dialog pop up 4. Create another list 5. Go to lists and view the list detail 6. See "Edit" dropdown and click "Delete Lists" button, see confirmation dialog pop up -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32