This is more of a fixit bug than a deputy task.

Also time started is not a fundamental feature of a AFE job:
describe afe_jobs;
+----------------------+--------------+------+-----+---------+----------------+
| Field                | Type         | Null | Key | Default | Extra          |
+----------------------+--------------+------+-----+---------+----------------+
| id                   | int(11)      | NO   | PRI | NULL    | auto_increment |
| owner                | varchar(255) | YES  | MUL | NULL    |                |
| name                 | varchar(255) | YES  | MUL | NULL    |                |
| priority             | int(11)      | YES  |     | NULL    |                |
| control_file         | text         | YES  |     | NULL    |                |
| control_type         | int(11)      | YES  |     | NULL    |                |
| created_on           | datetime     | YES  | MUL | NULL    |                |
| synch_count          | int(11)      | NO   |     | NULL    |                |
| timeout              | int(11)      | NO   |     | NULL    |                |
| run_verify           | tinyint(1)   | YES  |     | 1       |                |
| email_list           | varchar(250) | NO   |     | NULL    |                |
| reboot_before        | smallint(6)  | NO   |     | NULL    |                |
| reboot_after         | smallint(6)  | NO   |     | NULL    |                |
| parse_failed_repair  | tinyint(1)   | NO   |     | 1       |                |
| max_runtime_hrs      | int(11)      | NO   |     | NULL    |                |
| drone_set_id         | int(11)      | YES  | MUL | NULL    |                |
| parameterized_job_id | int(11)      | YES  | MUL | NULL    |                |
| max_runtime_mins     | int(11)      | NO   |     | NULL    |                |
| parent_job_id        | int(11)      | YES  | MUL | NULL    |                |
| test_retry           | int(11)      | NO   |     | 0       |                |
| run_reset            | smallint(6)  | NO   |     | 1       |                |
| timeout_mins         | int(11)      | NO   |     | NULL    |                |
| shard_id             | int(11)      | YES  | MUL | NULL    |                |
| require_ssp          | tinyint(1)   | YES  |     | NULL    |                |
+----------------------+--------------+------+-----+---------+----------------+
24 rows in set (0.01 sec)

The reason for this is its part of an AFE Host Queue Entry:
mysql> describe afe_host_queue_entries;
+------------------+--------------+------+-----+---------+----------------+
| Field            | Type         | Null | Key | Default | Extra          |
+------------------+--------------+------+-----+---------+----------------+
| id               | int(11)      | NO   | PRI | NULL    | auto_increment |
| job_id           | int(11)      | YES  | MUL | NULL    |                |
| host_id          | int(11)      | YES  | MUL | NULL    |                |
| status           | varchar(255) | YES  | MUL | NULL    |                |
| meta_host        | int(11)      | YES  | MUL | NULL    |                |
| active           | tinyint(1)   | YES  |     | 0       |                |
| complete         | tinyint(1)   | YES  | MUL | 0       |                |
| deleted          | tinyint(1)   | NO   |     | NULL    |                |
| execution_subdir | varchar(255) | NO   |     | NULL    |                |
| atomic_group_id  | int(11)      | YES  | MUL | NULL    |                |
| aborted          | tinyint(1)   | NO   | MUL | 0       |                |
| started_on       | datetime     | YES  |     | NULL    |                |
| finished_on      | datetime     | YES  |     | NULL    |                |
+------------------+--------------+------+-----+---------+----------------+
13 rows in set (0.00 sec)


The difficulty here is that there can be a 1 to many mapping of afe_job to afe host queue entries because a single job may run multiple test processes against multiple DUTs. So then there is a question of which afe host queue entry do you sort by if there are multiple?

Lastly when generating the UI pages we would then require the UI to do a DB join operation. This could be expensive and slow down the UI even more than it already is. 

Yes I agree it's not for the deputy.

I am sad that what I thought was a relatively simple request turns out to be borderline unreasonable! :)