When forcing an iteration with a non-final Custom Test Status, the Timer is reset.

Description

When forcing an iteration with a non-final Custom Test Status, the Timer is reset.

Pre-conditions

How to reproduce

1. Create a Test with Parameters and execute it
2. On the first iteration, force its status with Executing - The Timer starts counting as expected
3. Change the status to a custom non-final Test Status - The Timer is reset back to 0, and it does not start again.

Actual result/Attachments

The timer is not behaving equally for Custom Test Statuses as it works, for example, for Executing, a native one.

Check the gif below.

Expected result

Every non-final custom test status should behave exactly as Executing. The timer should start counting and not being reset.

Version

• Xray Cloud - v4.8.2-1

Workaround