Actions
Feature #37938
closedReject start-at dates in the past when a job is scheduled
Difficulty:
Triaged:
No
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.
Updated by The Foreman Bot almost 2 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-tasks/pull/763 added
Updated by The Foreman Bot about 1 year ago
- Assignee set to Adam Ruzicka
- Pull request https://github.com/theforeman/foreman-tasks/pull/768 added
Updated by The Foreman Bot about 1 year ago
- Pull request deleted (
https://github.com/theforeman/foreman-tasks/pull/763, https://github.com/theforeman/foreman-tasks/pull/768)
Updated by Adam Ruzicka about 1 year ago
- Pull request https://github.com/theforeman/foreman-tasks/pull/768 added
Updated by Pablo Fernández Rodríguez about 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset 3c94bc0aad2ab68dcfea8b36f01562b6b4ea5886.
Updated by The Foreman Bot about 1 year ago
- Pull request https://github.com/theforeman/foreman-tasks/pull/772 added
Updated by Adam Ruzicka about 1 year ago
- Fixed in Releases foreman_tasks-11.0.2 added
Actions