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

[Bug 37532] New: Protected status should have a permission to block editing patron
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '26

10 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37532 Bug ID: 37532 Summary: Protected status should have a permission to block editing patron 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, protected status prevents accidental deletion of a patron account. With bug 36085, an extra layer will be added to protect that status from being turned on or off with a permission. However, the account is not fully protected, as important information can be altered in the account by editing it. I would like to see an option for protected status, that would allow us to decide if this protected status will also prevent others from editing the account at all, unless they have the permission in bug 36085. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 40183] New: Record diff in action logs when editing notices
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40183 Bug ID: 40183 Summary: Record diff in action logs when editing notices Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 37940 Notices would be a good place to implement the diff column for action logs. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37940 [Bug 37940] [OMNIBUS] All modification logged via action logs should include original to create JSON diff -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 38296] New: Investigate DataTables's extension StateRestore
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38296 Bug ID: 38296 Summary: Investigate DataTables's extension StateRestore Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 33484, 36640 https://datatables.net/extensions/staterestore/index#Features Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33484 [Bug 33484] Ability to remember user's selected table configuration and search filters for tables https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36640 [Bug 36640] Upgrade DataTables from 1.13.6 to 2.x -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31159] New: Can we drop the 'CircSideBar' preference and convert the sidebar to being collapsible?
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31159 Bug ID: 31159 Summary: Can we drop the 'CircSideBar' preference and convert the sidebar to being collapsible? 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I find it confusing that the CircSidebar is disabled by default. I propose we enable it and remove the preference replacing it with a collapsible navigation that gives us the best of both worlds. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 40366] New: Update the label export process to avoid Greybox modal
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40366 Bug ID: 40366 Summary: Update the label export process to avoid Greybox modal Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org I propose that we update the label export process in order to avoid using a Greybox modal. We can just as easily move from page to page as the process progresses. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 27357] New: Trigger printing of a routing list, when an issue is received
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27357 Bug ID: 27357 Summary: Trigger printing of a routing list, when an issue is received Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment the printing of a routing list happens separately from receiving the issue and requires extra steps and attention to not be forgotten. It would be nice, if the printing of a routing list was triggered by receiving an issue to have a more streamlined process. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28628] New: Elasticsearch - Heading search form does'nt match related indexed heading
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28628 Bug ID: 28628 Summary: Elasticsearch - Heading search form does'nt match related indexed heading Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: alex.arnaud(a)biblibre.com When an authority is created using LinkBibHeadingsToAuthorities the heading created "700 $aVidard $bMathieu $f1971-..." (unimarc) is saved as "Vidard Mathieu 1971-..", indexed as "Vidard Mathieu 1971-.." and searched as "Vidard Mathieu 1971" => no match. So the link bib does'nt work. Test plan (UNIMARC exemple): - create a biblio with the following data in tag 700: - $a Vidard - $b Mathieu - $d 1971-... - save. => a new authority is created with the following heading "Vidard Mathieu 1971-.." - create an other biblio with the same value in tag 700. => again a new authority is created with the same heading. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 33835] New: [OMNIBUS] Move Breeding module to Koha namespace
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33835 Bug ID: 33835 Summary: [OMNIBUS] Move Breeding module to Koha namespace 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 19852] New: Add message text box in circulation for patrons does not accept HTML tags
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19852 Bug ID: 19852 Summary: Add message text box in circulation for patrons does not accept HTML tags Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: michael(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 69958 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=69958&action=ed… result after adding HTML tags for a patron message Hi When you add a patron message in circulation.pl, the modal that appears has a text box that does not accept HTML tags. Some libraries use HTML tags in these messages to link to information in Koha and to format the display of the message (see attached). Having this modal accept HTML would allow formatting and linking in messages. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 23978] New: notes field in saved reports should allow HTML
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23978 Bug ID: 23978 Summary: notes field in saved reports should allow HTML Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: theod(a)lib.auth.gr QA Contact: testopia(a)bugs.koha-community.org In recent Koha 18.11, parsing of HTML tags was removed from many fields for security reasons. However, as also seen in 22938, 22702, 22501, 23194, 23683 there are places where HTML (or at leas line breaks!) are required, or the output is too messy. The 'notes' field in the "Guided reports wizard › Saved reports" displays the data that is previously entered in a textarea. However, the guided_reports_start.tt does not parse the HTML (nor line breaks), so the output in the resulting table is all in one line! As with the other patches, I propose that we allow HTML in report notes, so one can use strong/italics/colors/urls in notes, and most importantly, line breaks! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48