Project

General

Profile

Actions
Copy link

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.

Status:
Closed
Priority:
Normal
Assignee:
Marek Hulán
Category:
-
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman-tasks/pull/161
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

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 issues 2 (0 open — 2 closed)

Related to Foreman Remote Execution - Feature #12815: On the job invocation index, show future start time for delayed executionClosedMarek Hulán12/14/2015Actions
Related to foreman-tasks - Bug #13238: start_at is not set for immediately triggered tasksClosedMarek Hulán01/15/2016Actions
Actions
Copy link
 #1

Updated by Marek Hulán almost 9 years ago

  • Related to Feature #12815: On the job invocation index, show future start time for delayed execution added
Actions
Copy link
 #2

Updated by The Foreman Bot almost 9 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-tasks/pull/161 added
Actions
Copy link
 #3

Updated by Marek Hulán almost 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Marek Hulán almost 9 years ago

  • Related to Bug #13238: start_at is not set for immediately triggered tasks added
Actions
Copy link

Also available in: Atom PDF