https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30300
Katrin Fischer <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Failed QA Keywords| |release-notes-needed --- Comment #19 from Katrin Fischer <[email protected]> --- I struggle a bit with this one in terms of having no regressions/confusion for libraries and I think this needs more work. 1) Regression (blocker) After updating, no MEMBERSHIP_EXPIRY notices will be sent as no patrons will have the flag in their patron accounts, even if it worked before. I don't have a good solution here. Maybe the best we could do is globally add the flag if MembershipExpiryDaysNotice is set to a value >= 1? I believe together with the where it would keep the current behavior? 2) Documentation (not blocker, but easy) It's not clear from the GUI that a "where" option might overwrite the setting in the patron account. I could have a patron with checked patron expiry notice, that is then "removed" from the list by a where parameter. I think at least a note on the system preference could help here to fight off general confusion. 3) Visibility of configuration option (blocker) I feel the visiblity of the messaging preference should be dependent on the MembershipExpiryDaysNotice system preference so libraries have the option to easily turn this feature off or "keep it invisible" after update. I hope I was not missing something! -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
