When calculating the status of a Test Run with multiple iterations, non-final custom statuses on iterations must not affect the final Test Run status

When there is a non-final status called "N/A" on a given Test Run iteration, this status is automatically set on the overall Test Run status. The N/A status usually means that the iteration is being skipped and should not be considered for the test's final result.

Nevertheless, we can also create another non-final status named "Blocked" which one can consider to block the whole Test Run.

Xray must provide a way to consider some status as skipped or N/A so that these do not affect the final status of the Test Run.