Test status is wrongly calculated in parameterized Tests

Description
Test status is wrongly calculated in parameterized Tests.

Pre-conditions

1. Create one custom Test Status - N/A as nonfinal and map it to Requirement Status OK.
2. Create one custom Test Step Status - N/A and map it to Test Status N/A

How to reproduce

1. Create a Test with one parameter with values A, B, and just one Test Step.

1. Execute this Test.

Actual result/Attachments

1. Set the step for iteration 1 as PASS - The iteration status will be PASS. The Execution status will be Executing - This is correct.
2. Set the step for iteration 2 as N/A - The iteration status will be PASS. The Execution Status will be PASS - This is wrong. The iteration status should be N/A.  

Expected result

1. Iteration 2 should be N/A. For that, it is necessary to go to the Test Status N/A and map it with Requirement Status Unknown. 
2. The Requirement Status must not affect this result.

Please see the gif attached, replicating this situation. 

Version

• 6.0.3