Feature #13001
closed
start_at should be filled in even for immediate tasks
Added by Marek Hulán almost 9 years ago.
Updated almost 9 years ago.
Description
Otherwise it complicates task searching and listing. Namely when printing this info we'd have to do start_at || started_at, for searching we'd have to write custom scoped_search method, for sorting we'd have to provide SQL snippet that would select the value that is present in ORDER BY.
- Related to Feature #12815: On the job invocation index, show future start time for delayed execution added
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman-tasks/pull/161 added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Related to Bug #13238: start_at is not set for immediately triggered tasks added
Also available in: Atom
PDF