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

[Bug 39179] New: ILL batches should allow editing without having to add new requests
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '25

29 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39179 Bug ID: 39179 Summary: ILL batches should allow editing without having to add new requests Change sponsored?: --- Product: Koha Version: 24.11 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: jeremy.evans(a)ukhsa.gov.uk, katrin.fischer(a)bsz-bw.de, martin.renvoize(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com, tomascohen(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 34250] New: Sort debit types alphabetically by description and add empty option when adding manual fee
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '25

29 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34250 Bug ID: 34250 Summary: Sort debit types alphabetically by description and add empty option when adding manual fee Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees 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 when you add a manual fee to a patron account the sorting is off, maybe sorting the system internal ones separately from additional debit types? There is also no empty entry, so the first is always selected automatically. It would be nice if we could select a 'default' that is pre-selected, but to avoid errors, and empty entry and making the field requires would be good. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 39491] New: All accoutnline notes should be HTML textarea
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '25

29 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39491 Bug ID: 39491 Summary: All accoutnline notes should be HTML textarea Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com Since accountline notes can be mediumtext in DB we should turn all the inputs on the UI into textarea to make it easier to enter and read notes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 39497] New: 'Lists' page tabs should be marked as such
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '25

29 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39497 Bug ID: 39497 Summary: 'Lists' page tabs should be marked as such Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Accessibility Assignee: koha-bugs(a)lists.koha-community.org Reporter: chloe.zermatten(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, oleonard(a)myacpl.org On the Koha OPAC, the 'Lists' page contains tabs which aren't clearly marked as such (no relevant attribute set on the element). This means that screen readers will not recognise the tabs as such, and screen reader users will not be made aware that these are available. Since the 'Advanced Search' page contains tabs that are correctly identified and described by screen readers, update the HTML for the tabs on the 'Lists' page so that it matches theirs. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 39323] New: Print dropdown in members toolbar should auto close
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '25

29 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39323 Bug ID: 39323 Summary: Print dropdown in members toolbar should auto close Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using the Print dropdown to print something from the patron's account (summary, slip, etc.) the dropdown no longer closes automatically when clicking an option. This leads to an awkward extra click to clear it away after closing the print dialog. To replicate - 1 - Pull up a patron 2 - Click Print > Print summary in the toolbar 3 - Close the print dialog 4 - The Print dropdown menu is still open -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 36932] New: koha-plack: Allow overriding starman environment for enabled dev_install
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '25

29 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36932 Bug ID: 36932 Summary: koha-plack: Allow overriding starman environment for enabled dev_install Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Allow to control these parts of the script in particular: if [ "$DEV_INSTALL" = "1" ]; then # Maybe we should switch off debug_mode if DEV_INSTALL is not set? environment="development" fi and if [ "$debug_mode" = "yes" ]; then environment="development" -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 53

[Bug 39501] New: Incorrect relationship code chosen when linking authorities with other authorities
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '25

29 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39501 Bug ID: 39501 Summary: Incorrect relationship code chosen when linking authorities with other authorities Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: a.roussos(a)dataly.gr QA Contact: testopia(a)bugs.koha-community.org Created attachment 180049 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=180049&action=e… Screenshot of the Staff interface showing the problem While working on something unrelated (Bug 21453), I noticed that in the current main branch, when linking authorities with other authorities, if you select a relationship you no longer get the associated letter (i.e. the "relationship code") copied to the appropriate subfield. Rather, the whole description gets copied. So, if you select "g - Broader term" (in MARC21), the following value gets copied to subfield $w: g - Broader term Instead of the correct value, which is simply: g The attached screenshot is an example of what I'm referring to. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 25733] New: Return claims attention can't be cleared
by bugzilla-daemon＠bugs.koha-community.org 29 Sep '25

29 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25733 Bug ID: 25733 Summary: Return claims attention can't be cleared Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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 The Attention notice on circulation.pl does not go down as claims are resolved, and there does not seem to be any way to reset this. The message won't even go away if you turn off the feature. This is very buggy. We need to have a way to remove a mistaken claim. We need to have a way to determine if certain types of resolutions count or don't count. This message should go away if claims returned is disabled. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 44

[Bug 23724] New: Toolbars should have distinct IDs
by bugzilla-daemon＠bugs.koha-community.org 28 Sep '25

28 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23724 Bug ID: 23724 Summary: Toolbars should have distinct IDs Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: hayleymapley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl The Cataloguing and Serials toolbars both have the ID of toolbar. IDs should be distinct to allow for easier styling. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 28970] New: Create runtime parameters on the fly
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '25

26 Sep '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28970 Bug ID: 28970 Summary: Create runtime parameters on the fly Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: george(a)nekls.org QA Contact: testopia(a)bugs.koha-community.org I was just thinking how helpful it would be if we could create runtime parameters inside of a report. What I'm thinking is something like this WHERE biblio.title LIKE CONCAT("%", <<Title contains one of these words|["good", "box", "friend"]>>, "%") creating a drop-down that has the three options: free, good, box. Being able to create parameters would open up a lot of new options with writing reports. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9