Stephen Solada
My feedback
3 results found
-
23 votesStephen Solada
supported this idea
·
-
352 votes
This is not something I have plans for in the near future because of the complexity and the wide other range of feature requests it would attract due to bigger clients (permissions, roles, audit logs, SSO, SLA, etc...). But I might do it at some point if I want to target bigger clients.
Stephen Solada
supported this idea
·
-
101 votes
Ok I'm moving this back to "under review" as it's gathering a lot of interest, but this would require first https://updown.uservoice.com/forums/177972/suggestions/16982392 and https://updown.uservoice.com/forums/177972/suggestions/15589635 to be implemented to provide a decent UI for this.
An alternative way to doing this now is to automate the check disable/mute on your end using the API, quite easy to do in a maintenance script: https://updown.io/doc/how-to-automate-check-disable
An error occurred while saving the comment Stephen Solada
supported this idea
·
This was the biggest thing we missed when evaluating this product. Being able to publish this would drastically help add context to the outages and also be a great place to post them for companies that host their own web sites. I have attached a quick sketch of what I think would be most helpful in our use case. In the example, when the window is over it would automatically move to the bottom of the page. It would also be nice to manually add past windows for emergency maintenance that was not previously scheduled.