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

[Bug 38149] New: Make ESLint config compatible with version 9 and have ESLint and Prettier installed by default
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38149 Bug ID: 38149 Summary: Make ESLint config compatible with version 9 and have ESLint and Prettier installed by default Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org To make it easier to check guideline JS8 https://wiki.koha-community.org/wiki/Coding_Guidelines#JS8:_Follow_guidelin… And be one step closer to able to enforce it on .vue and .ts files -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 42

[Bug 38546] New: prettierrc should set more settings
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38546 Bug ID: 38546 Summary: prettierrc should set more settings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org We don't even have the default indentation set to 4 spaces. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 38515] New: Generate next serial deletes the notes from the expected serial and ignores preference PreserveSerialNotes in the new serial
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38515 Bug ID: 38515 Summary: Generate next serial deletes the notes from the expected serial and ignores preference PreserveSerialNotes in the new serial Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: adolfo.rodriguez(a)xercode.es QA Contact: testopia(a)bugs.koha-community.org If a serial with the status Expected has notes and you click the "Generate next" button, the serial status will change to Late and the notes will be gone. If the system preference PreserveSerialNotes is activated, it won't have any effect, as the new serial won't keep the notes from the previous serial. This is cause by the call to the function ModSerialStatus at serials-collection.pl inside operation cud-gennext, that passes "" where the notes should go. This means that field will be deleted in the current serial with status 1 (Expected) and won't be copied to the new serial. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 38773] New: SMTP server is not showing on the library detail page
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38773 Bug ID: 38773 Summary: SMTP server is not showing on the library detail page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When an SMTP server is selected for a library, it is well displayed in the form to modify the library and in the list of all libraries (in column SMTP server) but when viewing a library detail (without editing) the line "SMTP server" is empty. To reproduce : 1- Create an SMTP server in Koha (it doesn't need to be valid) a- Go to Administration > Additional parameters > SMTP servers b- Click on "New STP server" c- Fill all mandatory fields (it doesn't need to be valid information) d- Click on "Submit" 2- Add the created SMTP server to a library a- Go to Administration > Basic parameters > Libraries b- Choose a library and click on Edit (in column "Actions") c- On the line "SMTP server" select the server created d- Click on "Submit" 3- Check the display a- Go to Administration > Basic parameters > Libraries b- Check that the name of the SMTP server you just selected is displayed in the column SMTP server c- Click on the name of the library you modified d- Check that the line "SMTP server" is empty e- Click on "Edit library" f- Check that the name of the SMTP server you just selected is still selected -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 29

[Bug 35826] New: Optimize building of holds queue based on transport cost matrix
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35826 Bug ID: 35826 Summary: Optimize building of holds queue based on transport cost matrix Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are several problems when building the holds queue which makes it hard for the libraries to predict the outcome for how items are allocated based on their configured policy. 1. The allocation of items should be done by optimizing on transport cost. Currently a greedy algorithm is applied when building the holds queue which doesn't always produce optimal results. 2. The allocation of items should not fall back to some default allocation if an allocation by using the transport cost matrix fails. If no allocation can be found that satisfies the configured constraints it is a violation of the configured policies o proceed and make an allocation. 3. Although items at the local library have transport cost 0, assigning local items should not be given absolute precedence. It is simply false that assigning local items "is obviously the least costly" as the comment says. (That we hard code the cost to 0 for local items is also an arbitrary restriction in Koha, there is no technical reason as to why we shouldn't allow the libraries to set a cost for allocating local items.) I am currently working on a solution based on the Hungarian Algorithm. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 75

[Bug 17437] New: Advanced cataloging editor - editing the 001 field overwrites data
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17437 Bug ID: 17437 Summary: Advanced cataloging editor - editing the 001 field overwrites data Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In the Advanced Cataloging Editor, when you add any data to the beginning of the 001 tag it types over the data already entered in the field. For example, adding the 'ocn' prefix to OCLC numbers in the advanced editor overwrites the first 3 digits of the OCLC number, causing you to reenter the data. In the basic editor you can enter data in the 001 without it overwriting an current data in the field. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 23674] New: Allowing editable notes when posting Payments/Writeoffs
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23674 Bug ID: 23674 Summary: Allowing editable notes when posting Payments/Writeoffs Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice if a librarian forgot to add a note to a payment/write-off/manual invoice transaction, or if a note was added at time of transaction, that this note is editable. Currently, this is not something that can be edited, therefore, a librarian would have to remove the entire transaction to edit the note. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 109

[Bug 31481] New: Pass message_id to SMS drivers
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31481 Bug ID: 31481 Summary: Pass message_id to SMS drivers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Most of the SMS Gateways support REST API and it is common that the operator sends their report back to the service. Now it is impossible to catch reports if sms was succesfully sent or it failed since we can't pass the message_id to our report url when sending the message to the gateway. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 16188] New: SMS via email not applicable in India due to telecom regulation
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16188 Bug ID: 16188 Summary: SMS via email not applicable in India due to telecom regulation Change sponsored?: --- Product: Koha Version: master Hardware: All URL: https://lists.katipo.co.nz/pipermail/koha/2016-April/0 45114.html OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Notices Assignee: indradg(a)gmail.com Reporter: indradg(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 9021 Due to the nature of telecom regulatory framework in India, bug 9021 will not work for 99% of 500+ million cell phones in India. Details as explained in this mail with specific examples - https://lists.katipo.co.nz/pipermail/koha/2016-April/045114.html This patch adds a "note" for such exceptions like India in the provider setup screen. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9021 [Bug 9021] Add SMS via email as an alternative to SMS services via SMS::Send drivers -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 32403] New: On Demand Messaging
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32403 Bug ID: 32403 Summary: On Demand Messaging Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: christofer.zorn(a)ajaxlibrary.ca QA Contact: testopia(a)bugs.koha-community.org We are a library that relies on both email messaging (through Koha) along with SMS and Phone messaging (through Twilio). We are very happy with the messaging features involved in Koha, but for me, there is something missing that could be improved. With the right system permissions, we'd like to see the ability to generate on demand messages to specific patrons, or even tailored messages to groups. While I understand that this isn't specifically what Koha is meant for, there are wider benefits to this that I think warrant a discussion. This is a means of interacting with a patron. While individual email is normally an option, in a mid to larger sized system where multiple staff can reply to a communal message, Koha has a tracking mechanism that would allow staff to see what information was sent to a patron by looking at the Notice tab. This could also morph into a marketing aspect of Koha where we could leverage the history and make this similar to Patron Point. Symphony has an on demand message sending tool, however from what I remember it was spotty. The tweak would be creating an interface that allowed inputting of information into the messaging table ... Please let me know if this is possible. Our library has had the need for this a couple of times, where we could take one last stab at reaching out to expired patrons (beyond what Koha is already doing), or communicating back to a patron through SMS when leaving a voicemail isn't an option. Thanks! Chris -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6