-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
scheduled maintenance #4474
Comments
Hey, I'm with you on this one, I think this could be better handled by adding another timestamp, as such: 1st Timestamp (Start time) The actual completion may stay null until set as complete, and as long as start and scheduled (or start only if there's no est. end) are set it can show on the status page If anyone has better ideas or suggestions please chime in, I could work on implementing this next week! |
i think that would be an perfect option ;-) |
Hmm, we recently changed scheduled maintenances to work the way you're seeing now, but I agree it may be a little confusing. I'm happy for someone to look into improving this further. |
I took a look at version 3 today and was a bit surprised that scheduled maintenance with a predefined time window (e.g., 08:00 AM – 10:00 AM) doesn’t show up in the status overview at all. For us, this kind of maintenance is the norm rather than the exception. When there's no predefined end time, it's usually more of an incident or emergency situation. We would really appreciate it if there were an option (like the one described above) to have clearly defined maintenance windows still appear on the overview page :) |
Hello,
if you plan an scheduled maintenance with an START and END date it will never appear on the dashboard.
Only if you create them with an START date only it will appear.
I think this is a bit confusing, because if i plan an schedule an weekly update, i want to declare an timeslot and dont want to enter again the cachet-scheduled-maintenance to enter an date at the end of my maintenance.
Can this function be controlled or changed?
Thanks
The text was updated successfully, but these errors were encountered: