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

[Bug 17858] New: Omnibus: Move staff client JavaScript to the footer
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '26

09 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17858 Bug ID: 17858 Summary: Omnibus: Move staff client JavaScript to the footer 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 Depends on: 17418 In order to conform to best practices for performance staff client template javascript should be in the footer instead of the header. This omnibus bug will collect reports which modify subsets of the staff client templates. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17418 [Bug 17418] Move staff client home page JavaScript to the footer -- You are receiving this mail because: You are watching all bug changes.

1 121

[Bug 18861] New: branch_transfer_limits needs keys
by bugzilla-daemon＠bugs.koha-community.org 09 Jun '26

09 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18861 Bug ID: 18861 Summary: branch_transfer_limits needs keys Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The branch transfers limits are edited in : /cgi-bin/koha/admin/branch_transfer_limits.pl This page calls a loop on IsBranchTransferAllowed with all destination branches and codes (ccodes or itemtypes). This can takes a huge time because table branch_transfer_limits has no keys. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 17656] New: Irregularities in serial prediction pattern are planned only for the current year
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '26

06 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17656 Bug ID: 17656 Summary: Irregularities in serial prediction pattern are planned only for the current year Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P2 Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When you se, through test prediction pattern, a serial pattern including planned irregularities (for example a 1/month serial that you know there's no issue on july), this is only valid fot the current subscription. Over the next renewal, you will have to set it again which is very tedious. We should be able to configure this in the long run (as it was possible in previous version of Koha before 3.14, I think) Olivier Crouzet -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 391

[Bug 19958] New: Allow the system preference AutoMemberNum to include a combination of numbers and letters when creating a new barcode
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19958 Bug ID: 19958 Summary: Allow the system preference AutoMemberNum to include a combination of numbers and letters when creating a new barcode Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently the system preference "automembernum" only allows for the patron's barcode to default the card number field on the patron addition screen to the next available card number (for example, if the largest currently used card number is 26345000012941, then this field will default to 26345000012942). It would be nice for the library to choose the format of the barcode (for example : system preference autobarcode). Then a library could choose to include letters and numbers to their patron's barcode instead of just numbers. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 19384] New: [OMNIBUS] Add Selenium tests
by bugzilla-daemon＠bugs.koha-community.org 02 Jun '26

02 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19384 Bug ID: 19384 Summary: [OMNIBUS] Add Selenium tests Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 17617] New: Confirmation e-mail to patron when hold is placed
by bugzilla-daemon＠bugs.koha-community.org 26 May '26

26 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17617 Bug ID: 17617 Summary: Confirmation e-mail to patron when hold is placed Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: sally.healey(a)cheshiresharedservices.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If an item is purchased from an online shop, the patron will receive a confirmation e-mail of their order. We would like to see something similar in Koha when a hold is placed. We think this would be useful to confirm some key points, for example: - confirm the hold has been added to the system - confirm the title details of the requested item - confirm the collection library - confirm the fee which will be charged for fulfilling the hold - confirm the fee which will be charged if the hold is not collected - explain how to cancel the hold if it's no longer required - explain how to make changes to the hold if any details (e.g. change collection library from AAA to BBB) alter - explain how the patron will be notified when the item is ready for collection There is already a system preference: emailLibrarianWhenHoldIsPlaced - which enables Koha to e-mail the library staff whenever a patron places a hold. Could the code behind this be adapted to e-mail patrons instead, perhaps? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 15792] New: Double-clicking the 'renew' button on circulation.pl will double-charge account management fee
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15792 Bug ID: 15792 Summary: Double-clicking the 'renew' button on circulation.pl will double-charge account management fee Change sponsored?: --- Product: Koha Version: 3.18 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com PREREQUISITES 1) Create an account type that has an enrollment fee, and create a borrower of that type. 2) Write off any account management fees charged to that borrower by the account creation. STEPS TO RE-CREATE 1) Change borrower's dateexpiry to make the borrower expired. 2) Paste borrower's card number into 'Check out' bar 3) A warning will appear saying that the borrower's account has expired, including a 'Renew' link. 4) Double-click the link 5) Check the borrower's fines. You will see two account management fees in a row. distinct from the fee that was written off just after the patron was created. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 19558] New: Link 130 uniform title authority record to 240 tag
by bugzilla-daemon＠bugs.koha-community.org 22 May '26

22 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19558 Bug ID: 19558 Summary: Link 130 uniform title authority record to 240 tag Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jbeno(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Uniform titles will link only to 130, 630, 730, and 830 tags. 240 tags are uniform title tags and should also be linked. In addition, the auto create function should but does not create a 130 uniform title authority from a 240 bibliographic entry. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 7

[Bug 19690] New: Smart rules: Term "If any unavailable" is confusing and just means No
by bugzilla-daemon＠bugs.koha-community.org 22 May '26

22 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19690 Bug ID: 19690 Summary: Smart rules: Term "If any unavailable" is confusing and just means No Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Pertains to Allow on shelf holds. Triggered by looking at bug 4319. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 42

[Bug 20813] New: Revamp user permissions system
by bugzilla-daemon＠bugs.koha-community.org 22 May '26

22 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20813 Bug ID: 20813 Summary: Revamp user permissions system 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Koha's current user permissions system is a bit convoluted and limited due to it's legacy where the permissions system was a simple set of flags. A second layer of sub-permissions were later added complication and obfuscation to the system. We should revamp the permissions system to be a more modern system and open the path to having unlimited nesting of sub-permissions instead of shoe-horning sub-permissions into the limited system we have. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 100