Bug 20917 - Improve email functionality relating to ILL requests
Summary: Improve email functionality relating to ILL requests
Status: RESOLVED DUPLICATE of bug 22818
Alias: None
Product: Koha
Classification: Unclassified
Component: ILL (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement with 15 votes (vote)
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks: 20923
  Show dependency treegraph
 
Reported: 2018-06-12 14:19 UTC by Andrew Isherwood
Modified: 2022-11-07 10:40 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Isherwood 2018-06-12 14:19:45 UTC
The ILL module has the ability to send emails containing details of requests to "partner" libraries. This functionality, though currently in the core ILL code, is actually only required by the "FreeForm" backend. It is surfaced in the UI as a form containing an email template and a multi-select to select the partners who will receive the email.

The email functionality offered by ILL, though functional, is lacking in some important respects, which this bug proposes addressing. Proposed enhancements, which are all inter-related, are:

- Move emailing functionality from the core ILL module to the FreeForm backend where it is actually used
- Email is sent independently of the Koha message queue, which is understood to be undesirable, this should be addressed
- As such, there is no ability for users to specify a default message template, using the Notices and Slips module, this should be addressed
- It is not possible for users to specify default "reply-to" addresses for all ILL related emails, currently the ReplyToDefault syspref is used, this should be addressed
- No message notification is sent to nominated staff when a request is modified, this should be addressed
Comment 1 Andrew Isherwood 2019-08-02 13:00:29 UTC

*** This bug has been marked as a duplicate of bug 22818 ***