Requirement Status should be based rather on the scheduled test runs then on linked tests

The Requirement ticket has 2 Fix Versions: 6.2.0 and 7.1.0
Only one Test Execution ticket is created with Fix Version 7.1.0
2 Tests that are linked to the Requirement are associated with this Test Execution ticket.
These tests are not yet run.

The Requirement Status field shows:

• 6.2.0 - NOTRUN
• 7.1.0 - NOTRUN

As no test runs were scheduled for 6.2.0 the expected statuses should be:

• 6.2.0 - UNCOVERED
• 7.1.0 - NOTRUN

The Requirement Coverage Strategy set to "Use versioned Test Executions for Requirement Coverage"

When this option is enabled, the Status of a Requirement for a specific Fix Version V is calculated based on the latest Test Run with Fix Version V of each associated Test. With this strategy, a Requirement can have different Statuses one for each Fix Version in the project.

We should make difference when test execution is scheduled, test run is created and not yet execuited, and when there is no test execution scheduled at all.