cachethq
Ignore `completed_at` time for schedules
We always set a completed_at time for schedules, as a maximum time when the schedule should be finished. With these where-statements, schedules with completed_at time aren't displayed.
@Wouter0100 this feels like maybe bespoke logic? I'm really unsure on how schedules should work for the general.
Me neither, but if I'm correct - this field was required in the past. Because of that, we started using as an estimation on when the schedule is about to end. Not sure what more information is needed? :-P
Reopening as this is still an on-going thing. We manually remove this code each time we update :-).
The thought for us is that we have a maintenance window from x to y. Where y is an end date/time estimation, so customers know when to expect the maintenance to end.
Thank you for your input on Cachet 2.x. We are shifting our attention and resources to Cachet 3.x and will no longer be supporting the 2.x version. If your feedback or issue is relevant to the 3.x series, we encourage you to engage with the new branch.
For more information on the Cachet rebuild and our plans for 3.x, you can read the announcement here.
We appreciate your understanding and look forward to your contributions to the new version.