Traceability Report is not correctly generated if some parent issues are not Requirements

Description

Traceability Report is not correctly generated if some parent issues are not Requirements.

How to reproduce

1. 4 issues of type Story (issue type mapped as requirement)
2. each one belongs to distinct projects (4 projects)
3. only proj for Req 1 and proj for Req 2 are enabled for Xray coverage.
4. link type is caused by is configured under Xray Issue Type Mapping to set the hierarchy (parent-> child).
   Build the following hierarchy:

Story 1 (Not req) -> is caused by -> Story 2 (Not Req) -> is caused by -> Req 1 - > is caused by -> Req 2 - > is tested by -> Test 1.

Actual result/Attachments

• When generating the report, it says there are no requirements, which is wrong. The problem is that *Xray is not ignoring the "parent" issues (which are not requirements since the coverage is not enabled), linked with the same link type configured in Xray configs.
• If we break the link between Story 2 (Not Req) and Req 1, then the report is correctly generated since the Req 1 is now the Parent issue.

Expected result

Xray should be able to ignore all the issues linked with the same link type if the projects are not enabled for Xray coverage.

Version

• 6.2.3