Summary: | Use current patron contact info when resending notices | ||
---|---|---|---|
Product: | Koha | Reporter: | Christopher Brannon <cbrannon> |
Component: | Notices | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED FIXED | QA Contact: | Testopia <testopia> |
Severity: | major | ||
Priority: | P5 - low | CC: | emily.lamancusa, george, lauren_denny, lucy.vaux-harvey, susan.merner |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11556 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14855 |
||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Christopher Brannon
2022-11-08 18:05:20 UTC
Being able to re-send a message with updated contact information would be awesome. This would be a really great enhancement for a lot of libraries This would be helpful if a user requests login details or when user has a new card (it does happen). More control over the sending out of notices with ability to see this "welcome" and "Expiry" in the user preferences would be very useful as well. The welcome gets missed if a user account is saved before an email is added so again the availability to force a welcome email to be sent after an email is added would help. Failed emails (bouncebacks) could also merit from being able to resend a welcome once the email is corrected.... It is especially troublesome if you enter a patron email address incorrectly, and hit save, and the welcome message bounces. Great. Maybe staff realize the entered incorrectly and fix it, but the resend in the notifications is misleading. As admin, I know I can go to More and send a new welcome message, but most staff are not going to get that. We NEED to have resend work with current patron info, not saved info. Current name, current contact info, current address, etc. It seems at some point this was fixed. Not sure when. But is not an issue in 23.05, after doing some recent tests. |