It should be possible to have an option similar for iterations, like we have for Tests, where the Final Status from iterations should have precedence over the non-final

It should be possible to have an option similar for iterations, like we have for Tests, where the Final Status from iterations should have precedence over the non-final.

Currently, when forcing an iteration with a Non-Final Status, this Status directly contributes to the Overall Test Run Status. This means that if the non-final has a higher rank than the Final one, the non-final is the one that will prevail.

Consider the example below:
We have two iterations, and the first one should be discarded N/A (seen as PASSED) for the overall Status of the Test, while the second one is PASSED. The final status of the Test is N/A, and it should be possible to be PASSED, in case we choose to ignore the Non-Final ones: