Actions
Feature #37938
openReject start-at dates in the past when a job is scheduled
Status:
Ready For Testing
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Pull request:
Description
Problem Statement
If a job is scheduled by using `API` or `hammer` and by mistake `start-at` is in the past, the job will be executed immediately. Which most probably is not desired.
Requirements
I would expect the request to be rejected asking to use a valid date.
Actions