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

[Bug 29222] New: OMNIBUS: Replace the use of jQueryUI
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29222 Bug ID: 29222 Summary: OMNIBUS: Replace the use of jQueryUI Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org jQueryUI is no longer being developed: https://blog.jqueryui.com/2021/10/jquery-ui-1-13-0-released/ "our goal is to move it more to a maintenance state: we’ll make sure the library is compatible with new jQuery releases and that security issues are fixed but no new significant feature work is planned." I would like to start replacing jQueryUI dependencies, especially where there is a Bootstrap component which matches. - Accordion - Administration -> Table settings - Patrons -> Patrons requesting modifications - OPAC Can be replaced with Bootstrap "Collapse" component. - Autocomplete - Checkout and patron header searches - Article request patron search - Course reserve instructor search - Holds patron search - UNIMARC 210c plugin - UNIMARC 225a plugin No Bootstrap option. Possible candidate: https://tarekraafat.github.io/autoComplete.js/. - Tabs - (Lots) Can be replaced with Bootstrap tabs. - Sortable - Administration -> MARC frameworks -> Subfield structure -> Tab reordering. - Administration -> Authority types -> Subfield structure -> Tab reordering. - Administration -> System preferences -> Language and OPACLanguage reordering - Cataloging -> Basic MARC editor -> Subfield reordering. - Tools -> Stock rotation -> Stage reordering. No Bootstrap option. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 23205] New: Batch item operations should be available to report which return barcodes
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23205 Bug ID: 23205 Summary: Batch item operations should be available to report which return barcodes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 23197, 19233 Target Milestone: --- Currently batch operations can be applied to report results which include an itemnumber column. The same should be made available to reports which include a barcode column. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19233 [Bug 19233] Add ability to send itemnumbers in report results to batch modification https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23197 [Bug 23197] Add more batch operation options to SQL report results -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 38529] New: Optionally force uppercase callnumbers
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38529 Bug ID: 38529 Summary: Optionally force uppercase callnumbers Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be helpful to have something like uppercasesurnames but for item call numbers. Force anything entered into the call number field in the staff interface to be uppercase an also add something to the store item routine to catch and correct values there. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 27108] New: Update team for 21.05 cycle
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27108 Bug ID: 27108 Summary: Update team for 21.05 cycle Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We need to update the docs/teams.yaml file to capture the 21.05 team for the 20.11 release. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 14787] Allow confirm/continue option to circulation warnings at checkout
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

1 0

[Bug 37682] New: Improve speed of koha-preferences CLI tool (by lazy-loading modules)
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37682 Bug ID: 37682 Summary: Improve speed of koha-preferences CLI tool (by lazy-loading modules) Change sponsored?: --- Product: Koha Version: Main 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org By lazy loading C4::/Koha:: modules in the koha-preferences tool, so that they're only used by setter commands, we're able to gain enormous speed improvements for the getter commands. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 37657] New: koha-list --elasticsearch is super slow
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37657 Bug ID: 37657 Summary: koha-list --elasticsearch is super slow Change sponsored?: --- Product: Koha Version: Main 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: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If you have a large number of instances on a server, "koha-list --elasticsearch" takes a very long time to run. I think it's about 1-2 seconds per instance. That probably doesn't sound like much, but if you multiple it against a large number then it starts adding up. If it's run as part of an "apt-get install koha-common", that means that you've got a lot of downtime for what should be a very simple task. It's not an urgent issue, but I figure at some point I'll look at optimizing this lookup. The fun part with apt-get install koha-common is that "koha-list --elasticsearch" gets run 2 times. On some test machines I'm running, the slowest part of an update is "koha-list --elasticsearch". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 37495] New: Add ability to specify a single plugin to run for plugins_nightly.pl
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37495 Bug ID: 37495 Summary: Add ability to specify a single plugin to run for plugins_nightly.pl Change sponsored?: --- Product: Koha Version: unspecified 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice to have the ability to specify a single pluign for plugins_nightly.pl to run for a few reasons: 1) It would be very useful for development and testing 2) It gives the ability to run different nightly triggers at different times 3) Some other third thing -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 38525] New: Borrower Loan Table Does Not Update on Detail Page After Loan Changes
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38525 Bug ID: 38525 Summary: Borrower Loan Table Does Not Update on Detail Page After Loan Changes Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: somesecretemail(a)mailinator.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Description: There is an issue with the table displaying a borrower's loans on their detail page. After making changes to a patron's loans, such as checking in or out an item, the table does not update automatically. To see the updated table, the user must perform a hard refresh (Ctrl + F5 on Windows). This behavior is inconvenient and may confuse library staff. Steps to Reproduce: 1. Navigate to a borrower's detail page: https://host/cgi-bin/koha/members/moremember.pl?borrowernumber=:borrowerNum… 2. Click on the Check Out tab. 3. Observe the number of loans displayed: - In the checkout table at the bottom of the page. - In the tab label (e.g., "Checkouts (2)"). 4. Check out an item to the borrower. Actual Result: The tab label updates correctly (e.g., "Checkouts (3)"). The checkout table does not reflect the new loan. It still displays the previous number of rows. Expected Result: The table showing the patron's loans should update to reflect the new loan immediately (e.g., three rows if three items are checked out). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 7376] Transfer limits should be checked at check-in
by bugzilla-daemon＠bugs.koha-community.org 25 Nov '24

25 Nov '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7376 --- Comment #129 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- (In reply to Mathieu Saby from comment #128) > Would it be possible to see this feature in 25.05 ? You might want to drop an email to the developer directly. There hasn't been any action on the patches since January 2023. Considering the pace Koha's code moves there is probably more work needed now. -- You are receiving this mail because: You are watching all bug changes.

1 0