Steps to reproduce:
1. Start a workflow on an event
2. Have a look at job.getDateStarted() while the workflow is running
The job.getDateStarted() for the START_WORKFLOW job (job representing the workflow) changes over time. It seems to be set to the job.getDateStarted() of the most recently started sub job.
The job.getDateStarted() for the START_WORKFLOW job (job representing the workflow) should be initialized once when the job is started and remain then.
Workaround (if any):
ServiceRegistryInternal updates DateStarted of jobs with status RUNNING regardless of whether it has been previously set. I guess most operations other than START_WORKFLOW don't get updated once running. The error in also present in 4.x and 5.x
Side note, I think we are storing an unnecessary date field; the queue time can be derived from the created and start dates.
This ticket did something similar for the completion dates
I'm going to submit against 5.x as was also