Closed julienlafont-tabmo closed 2 years ago
@julienlafont-tabmo ouch, I feel your frustration. I think a combination of the first the second option makes the most sense: allowing you to run the check "ad hoc" but still reminding you a maintenance window is under way.
@orcunilbeyli @kiroushi we should add a small banner or similar to the top across the whole app that a maintenance window is active. Javier already had a small proposal. Ideally, the banner would show the name of the maintenance window.
@julienlafont-tabmo we now shipped an improvement around this topic: a banner will alert any user of an upcoming or ongoing Maintenance window, with a link to edit the window if they wish to do so. Thanks again for the feedback !
Is your feature request related to a problem? Please describe. I was working on a check yesterday. My usual workflow is to push a teardown script, run one of the checks, and see the result.
But suddenly running any check didn't work anymore.
I spent 1 hour looking for why my checks were not working anymore, looking for a problem in my script... It turns out that the checks were not executed because I had a maintenance period active which automatically activated in the middle of my tests
Describe the solution you'd like There should be clear visual feedback if a run is not executed because a maintenance period is active.
The UI should either display an explicit message or prevent the run from being executed.
OR, only automatic runs should be affected by the maintenance period, not manual runs (I see many use cases where it would be interesting to run the checks manually, to make sure that a commit did not create regression during an update, before closing the maintenance for example)