Enforce daily time window for performing and submitting cluster checks
As an on-duty checker or team lead,
I want the system to enforce a strict daily time window during which checks can be started and results submitted, with clear countdown timers,
so that checks are performed consistently within the agreed operational window and late or early submissions are prevented.
Key functionality:
Administrators can configure the daily time window for checks (default example: 09:00 – 10:30).
Checks cannot be started before the window opens or after the hard cutoff time.
A visible countdown timer shows:
Time remaining until the check window opens (when viewed before 09:00)
Time remaining to start a check, including a minimum buffer (e.g. checks must be started with at least 20 minutes remaining to allow completion)
Once a checker starts a check, a second countdown appears showing the time remaining until the hard submission deadline (e.g. until 10:30).
The system prevents submission of results after the configured cutoff time.
Clear visual indicators and warnings are shown on the dashboard and in the CLI when the user is approaching or outside the allowed window.
Attempting to start or submit outside the allowed time results in a clear, helpful error message explaining why it is blocked.
Administrators have the ability to grant a one-time extension or override for exceptional circumstances, with an audit log of the override.
Enforce daily time window for performing and submitting cluster checks
As an on-duty checker or team lead,
I want the system to enforce a strict daily time window during which checks can be started and results submitted, with clear countdown timers,
so that checks are performed consistently within the agreed operational window and late or early submissions are prevented.
Key functionality:
Administrators can configure the daily time window for checks (default example: 09:00 – 10:30).
Checks cannot be started before the window opens or after the hard cutoff time.
A visible countdown timer shows:
Time remaining until the check window opens (when viewed before 09:00)
Time remaining to start a check, including a minimum buffer (e.g. checks must be started with at least 20 minutes remaining to allow completion)
Once a checker starts a check, a second countdown appears showing the time remaining until the hard submission deadline (e.g. until 10:30).
The system prevents submission of results after the configured cutoff time.
Clear visual indicators and warnings are shown on the dashboard and in the CLI when the user is approaching or outside the allowed window.
Attempting to start or submit outside the allowed time results in a clear, helpful error message explaining why it is blocked.
Administrators have the ability to grant a one-time extension or override for exceptional circumstances, with an audit log of the override.