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

[Bug 42798] New: Public lists which allow changes to contents from anyone seeing this list do not allow anyone to change contents
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42798 Bug ID: 42798 Summary: Public lists which allow changes to contents from anyone seeing this list do not allow anyone to change contents Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: bibliothek(a)th-wildau.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Public lists allowing 'Anyone seeing this list' should allow at least a logged in anyone to add items to that list. to create: - create a public list for user koha via More -> Lists -> New List - set 'Public' to 'Public' and 'Allow changes to contents from' to 'Anyone seeing this list' - add some titles to this list f.e. search catalog for 'perl' -> select some -> Add to list -> the public list - login via another user to the opac - search for a title not on that public list - try adding it to the public list via 'Save to lists' or 'Add to list' - Sorry, you cannot add items to this list. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 36930] New: Item search gives irrelevant results when using 2+ added filter criteria
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36930 Bug ID: 36930 Summary: Item search gives irrelevant results when using 2+ added filter criteria 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: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the Item search a librarian is allowed, in the first step, to define additional filters like Title, Author, Publisher, Publication date etc. (the third fieldset). This works fine but only for one criterion. If one adds two or more criteria, the filter does not apply at all. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 36164] New: Bring more consistency to our module landing pages
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36164 Bug ID: 36164 Summary: Bring more consistency to our module landing pages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface 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 Koha's modules have a variety of landing page designs. We should try to move to a more consistent approach across landing pages. This bug serves as a collector for such work. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 21482] New: Create a "landing page" for ILL
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21482 Bug ID: 21482 Summary: Create a "landing page" for ILL Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no Currently, when you go to the ILL module, the first iew is of all ILL requests. This can be a lot of data, and take several seconds to load, and I doubt a lot of people will want the full list. So maybe we could have some sort of intermediate page with links to selections of request, based on their status, type etc. At it's simplest this could just be a page that displays the contents of a syspref, and that syspref could then be filled with HTML and links to filtered views of ILL requests. If the syspref is empty, the intermediate page could redirect to the full view, as it is today. A more advanced version would have a GUI to configure the links, order them, give them names etc. Thougts? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 43651] New: Clarify "Expand all" and "Collapse all" link labels in Acquisitions and Funds sections
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43651 Bug ID: 43651 Summary: Clarify "Expand all" and "Collapse all" link labels in Acquisitions and Funds sections Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: anneli.osterman(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- In the Acquisitions and Funds sections of Koha, there are "Expand all" and "Collapse all" links displayed above the budget table. These links are used to show and hide sub funds. The current labels are too generic and may be misunderstood by users, as they could be interpreted as expanding or collapsing all content on the table rather than specifically sub funds. To make the functionality clearer, the labels should be changed as follows: Expand all → Expand all sub funds Collapse all → Collapse all sub funds Steps to Reproduce: 1. Navigate to the Acquisitions or Funds section in Koha. 2. Locate the "Expand all" and "Collapse all" links above the budget table. 3. Observe that the labels do not clearly indicate that they affect only sub funds -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 6473] Test bug for Git-bz ✔ ❤ ★
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6473 Jonathan Druart <jonathan.druart(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6473] Test bug for Git-bz ✔ ❤ ★
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6473 --- Comment #457 from Jonathan Druart <jonathan.druart(a)gmail.com> --- Created attachment 206897 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206897&action=e… Bug 6473: test Signed-off-by: Jonathan Druart <jonathan.druart(a)gmail.com> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6473] Test bug for Git-bz ✔ ❤ ★
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6473 Jonathan Druart <jonathan.druart(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #206894|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 43594] New: Virtual barcode add to wallet option
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43594 Bug ID: 43594 Summary: Virtual barcode add to wallet option Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: catherine.micklethwaite(a)nhs.net QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- The virtual barcodes are great, but we need a more streamlined way to add them to a wallet on a mobile phone, the current process is complex and fiddly and it puts our users off using the virtual barcode. We want to go card free! Could we have a simple option for the patron that says 'Add to wallet' and it directly imports the barcode into either Google or Apple wallets -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 42036] New: Add diff support to REPORTS action logs
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '26

28 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42036 Bug ID: 42036 Summary: Add diff support to REPORTS action logs Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Blocks: 37940 The action logging for saved reports does not pass the $original parameter to logaction(), so no structured diff is generated in the action_logs.diff column. Currently log entries store the report name and SQL concatenated as a plain string. Affected calls: - reports/guided_reports.pl MODIFY (~line 250): logaction( "REPORTS", "MODIFY", $id, "$reportname | $sql" ) (no $original; only post-change state captured as a string) - reports/guided_reports.pl ADD (~line 594): logaction( "REPORTS", "ADD", $id, "$name | $sql" ) - C4/Reports/Guided.pm DELETE (~line 798): logaction( "REPORTS", "DELETE", $id, $data->report_name . " | " . $data->savedsql ) This bug covers updating these calls to pass structured hashrefs (e.g. { report_name => ..., savedsql => ... }) as $infos and, for MODIFY, the pre-change report data as $original, enabling proper before/after diff display in the action log viewer. 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 watching all bug changes. You are the assignee for the bug.

1 17