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

[Bug 31118] New: Allow to send the TOTP token when enabling 2FA
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '26

25 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31118 Bug ID: 31118 Summary: Allow to send the TOTP token when enabling 2FA Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Depends on: 28787 Bug 28787 adds the ability to send the token by email on login, but it would be great to have it available when we enable 2FA as well. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28787 [Bug 28787] Send a notice with the TOTP token -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 28437] New: Provide 'print' as an option for patron messaging
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '26

25 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28437 Bug ID: 28437 Summary: Provide 'print' as an option for patron messaging Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org While 'Hold ready' and 'Overdue' notices fallback to print, other patron messages cannot be selected with 'print' as the message transport. Users can, however, define print notices for any letter code, indicating they are an option to generate. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31263] New: Curbside pickups - Should the patron be able to alert even if not staged
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '26

25 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31263 Bug ID: 31263 Summary: Curbside pickups - Should the patron be able to alert even if not staged 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 30650 The patron can alert staff of their arrival only if the pickup is "staged and ready". Is that the expected behaviour? Do we want them to be able to alert even if it's still not ready yet? Do we need a syspref (or per library, in the admin) to control that? Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30650 [Bug 30650] Convert the Curbside Pickup plugin to Koha core -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 31266] New: Curbside pickups - New messaging preference
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '26

25 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31266 Bug ID: 31266 Summary: Curbside pickups - New messaging preference 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 30650 Bug 30650 is adding a new notice that is sent when a new curbside pickup is created. It's is generated when the patron has the "Hold filled" messaging preference. To add flexibility we could have a separate one, dedicated to curbside pickups. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30650 [Bug 30650] Convert the Curbside Pickup plugin to Koha core -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[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 23650] New: Multiple opac-restrictedpage.pl pages
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '26

23 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Bug ID: 23650 Summary: Multiple opac-restrictedpage.pl pages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Would like there to be the option to create multiple opac-restrictedpage.pl pages so that depending on patron or library, this information could be custom. Would need: * A way to identify and code for each page * A way to specify which patron types or branches could access each page. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 20628] New: Search result highlighting not working with truncated search terms
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '26

23 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20628 Bug ID: 20628 Summary: Search result highlighting not working with truncated search terms Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This specific issue may fall within the bounds of this larger bug: Bug 11270 - Search Result highlighting should be refactored https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11270 Search terms are not highlighted in search results if the terms are truncated. For example, the search kw:mold will show results with every instance of "mold" highlighted, even if it appears within a larger string like "molding." But a search for kw:mold* or kw,rtrn:mold will not show any highlighting in the search results. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4