Provide the ability to disallow the execution of a TCER with specific iterations until its test case is approved

If you enable a precondition with an iteration (using "When" and that iteration is set as the current project iteration, the precondition will apply to every artifact, regardless of "attributes" of that artifact. For example - a precondition on test case using an iteration. A test case execution record may or may not have an iteration set but if a test case precondition like Disallow Execution Until Test Case is Approved is set with an iteration that is iteration is the current project iteration then all test case execution is prevented if the test case is not approved. It does not matter if the TCER for the test case has a different iteration or no iteration at all. This calls into question why the option to use "during a specific timeline or iteration" is even available for test case execution. A test plan with a test schedule may have test cases using different iterations and the precondition is as-is cannot be used to prevent execution of only those defined by the pre-condiontion

The use case scenario needing to be supported is the following:

(1) A test case gets created.

(2) A TCER is generated from the step #1 test case with an iteration value of "Dry Run Iteration".

(3) The TCER from step #2 is executed one or more times.

(4) Later in time a second TCER is created against the test case from step #1. This TCER will have an iteration value of "Acceptance Iteration".

(5) A user attempts to run the "Acceptance Iteration" TCER but is prevented from doing so because its test case has not been approved.

(6) A user attempts to run the "Dry Run Iteration" TCER and is able to do so because the state of the test case does not affect this TCER's ability to be executed.

(7) The test case from step #1 is approved.

(8) A user attempts to run the "Acceptance Iteration" TCER and is able to doing so because the state of the test case is approved.