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

[Bug 30013] New: Limit/throttle SMTP connections
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30013 Bug ID: 30013 Summary: Limit/throttle SMTP connections 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: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org We have a setup where Koha is sending email through the SMTP server of the library's mother institution. We are seeing a problem with sending lots of emails in one go, where the first emails are sent ok, but then the rest fail with an error like this: unable to establish SMTP connection to (mail.x.y) port 25 It looks like this is due to some limit on the server, making it unresponsive if there are too many connections from the same source in a short time. I don't know a lot about SMTP but I can imagine a couple of solutions: - Introduce a configurable "sleep" period between each call to the external SMTP server (or batches of a configurable number, with a configurable sleep between each batch) - Looking at the response from the server and if "unable to establish SMTP connection" is received, wait for a configurable amount of time before trying to resend the failed message and the rest of the queue -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 25466] New: Review 'problem_reports' column names and types
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25466 Bug ID: 25466 Summary: Review 'problem_reports' column names and types 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org reportid => id borrowernumber => patron_id (created_by_id?) branchcode => library_id problempage => problem_page status => Looks like an ENUM About borrowernumber, I'm not sure it should default to 0, we are leaning to default to NULL. In the code it would probably default to the anonymous patron id? I might be wrong, just putting my notes here for discussion. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 25215] New: 'Report a problem' could be enhanced to become a generic 'Inquiry management' process.
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25215 Bug ID: 25215 Summary: 'Report a problem' could be enhanced to become a generic 'Inquiry management' process. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: oleonard(a)myacpl.org, testopia(a)bugs.koha-community.org Depends on: 4461, 25213, 25214 With bug 4461 we introduce a mechanism for patrons to report issues with the OPAC and for staff to manage the progress of such inquiries through various status's. We could generalize the code used to allow for other types of inquiries from patrons. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4461 [Bug 4461] Context-sensitive report a problem screen https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25213 [Bug 25213] It would be beneficial to be able to notify the patron of a resolution https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25214 [Bug 25214] It would be beneficial for patrons to be able to see their OPAC problem reports -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 27052] New: OPACReportProblems
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27052 Bug ID: 27052 Summary: OPACReportProblems Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Should give admin the ability to define who gets the e-mail/what e-mails to use. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 4461] Add a context-sensitive report a problem process
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4461 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|34255 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34255 [Bug 34255] Add an enquiry/request/workflow management module -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 4461] Add a context-sensitive report a problem process
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4461 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |34324 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34324 [Bug 34324] Merge OPACProblemReport and CatalogConcern functions -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 4461] Add a context-sensitive report a problem process
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4461 Martin Renvoize <martin.renvoize(a)ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |27052 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27052 [Bug 27052] Specify which email address is used by OPACReportProblems -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 5343] Subscription cost (Link serial and acqui modules)
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5343 Jonathan Druart <jonathan.druart+koha(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |30451 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30451 [Bug 30451] Delete a subscription deletes the linked order -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 34308] New: Item->store tests on itemlost>0
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34308 Bug ID: 34308 Summary: Item->store tests on itemlost>0 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Should store test itemlost > 0 or !itemlost (truth test) ? In most code it seems to be tested with truth already. It looks like we do not have any special meaning for negative itemlost values. There is normally just 1 to 5. So I think that the >0 test just stems from seeing values 1 and higher. So imo we can just test truth to see if something is lost. Do you have any feedback about these negative lost values? Please add it here. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 33208] New: When a recalled item is checked-in there is no indication of that the item is recalled and the recall status is not updated from requested
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33208 Bug ID: 33208 Summary: When a recalled item is checked-in there is no indication of that the item is recalled and the recall status is not updated from requested Change sponsored?: --- Product: Koha Version: 22.05 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: rajujogi.t(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4