Requirement Status is calculated as NOTRUN but should be OK when child requirement has tests out of Test Plan scope

Requirement Status is calculated as NOTRUN but should be OK when child requirement has tests out of Test Plan scope.

Steps to reproduce:

1. Create Test Plan TP
2. Create Story "S1"
3. Create Story "S2" and link it with a Child -> Parent Link to "S1". You now have S1 as parent requirement of S2
4. Create a Test TS1 and link it to S1
5. Create a Test TS2 and link it to S2
6. Add TS2 to TP and Execute it to PASS
7. Check Requirement status table in S1 for Scope Test PLan with TP, it shouldshow TS1 as PASS and TS2 as N/A and it should have OK as aggregate results but it shows NOTRUN. This would be OK for version scope, but not for TP.