Details
Minor
Description
Set up a scheduled reminder and configure it to use an absolute date rather than any of the relative data options.
If you then try to enable any repeat functionality for that reminder the interface allows the user to set up the repeat options, but these changes are then not saved.
I can't see any reason why it should not be possible to have a reminder triggered to fire on a given date and then repeat, for example, every two weeks after that. Indeed this seems like a fairly common use case.
Consequently I'm logging this as a bug rather than a feature request.
Stack Exchange question: http://civicrm.stackexchange.com/questions/15773/why-cant-i-set-up-a-repeating-scheduled-reminder-with-an-absolute-date
Attachments
Issue Links
- links to
Activity
I'll raise this with the client I have for whom this is an issue. However as a small organisation it's unlikely that they'll have budget for this type of project. What would be helpful is some sort of cost estimate for the work involved.
As I'm not a developer I'm not in position to submit a pull request.
In the interim I do think that it is misleading to users that the interface allows users to set an absolute date but does not disable or otherwise flag up the futility of configuring the repeat functionality when an absolute date is set. Perhaps simply adding an explanatory note in the UI to let users know of this limitation until a fix is implemented would go some way to reducing user frustration at something that otherwise behaves as if it is broken (which it is).
Graham Mitchell on further debug, it seems that we can allow is_repeat functionality with absolute date but that will require test coverage (asserting mail logging on different timeline on repeating reminders) for sure, to ensure its safe and won't cause regression to any SR supported entities. Rough estimate would be then 5-6hr. What ya say ?
Submitted PR https://github.com/civicrm/civicrm-core/pull/9773
As a lower-priority unfunded issue, this can be moved forward by either: