Currently when re-launching a test run the updated time is incorrect.

[vhd-lewis]

Describe the bug Currently when relaunching a test run the updated time is way long than it should be. My guess is it's working out the time from when the run was first started to when the run was then finished.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior When relaunching a run I would expect the run time to reflect as the original + the new launch total. Not the entire time between the relaunch also.

Screenshots

Desktop (please complete the following information):

• OS: Mac OS
• Browser chrome

[poliarush]

@littlefrontender is this backend?

[vhd-lewis]

@Fro0z1k @littlefrontender Is there an estimated completion date for this?

[poliarush]

@vhd-lewis we will try to look at it in current release.

[vhd-lewis]

@poliarush Do you have an rough estimate when your planning the current release?

[poliarush]

nope we don't put exact esitmates here as we have common backlog and it will be processed once we're ready to pick up such priority tickets. however, we will try to fix it in next 1-2 weeks.

[trumenov]

launched_at, duration_tracked, add in table Execution time with Launched_at...Finished_at

[vhd-lewis]

Any update on this at all? Just as it's been 3 weeks.

[TetianaKhomenko]

Hi @vhd-lewis! Thanks for reporting the issue. The fix will be published in the upcoming release.