Incorrect build durration reported when job is concurrent and queued

I have a bamboo job that I set up to run concurrently however I only have a single agent that is configured to run it. The reason I do this is because I am hosting a performance testing environment and the agent itself acts as the "gatekeeper" to insure that one and only one job runs within the environment at a time.

In order to allow my users to submit their jobs whenever they would like to, I configured the plan to run concurrently. As mentioned above, concurrency is not really possible because only one agent can run this job.

I noticed that when jobs are queued, the durration reported for them begins at the moment the job was submitted, NOT when the job started executing. I believe this to be incorrect behavior. I believe that the value of durration should report the time the job was actually executing, without adding in the time that it was queued waiting for an agent.