As a Project Admin, I should be able to decide if Epic/Story and Issue/Sub-task relations should be considered for requirements hierarchy.

Description
Previously, team-managed projects did not support epic/story relationships nor task/subtask. Therefore, these options were missing, because hierarchy was only possible if we used the link type configured.

User friction
Project admins currently have no option to enable/disable Epic/Story and Issue/Sub-task relationships when generating the requirements hierarchy.

Steps to reproduce (right now):
1. Create a team-managed project
2. Open Space Settings
3. Go to Xray Settings
4. Go to Test Coverage

Actual Result:
These options are not present in the Test Coverage Settings. The project admin has no option to decide to disable it. 

IMPACT

What would improve if solved:
Project admins can configure projects to allow Xray to consider the “implicit” dependencies that Jira establishes between Epics and children or Work items and their sub-tasks.

Impact on stakeholders:
Project admins gain more flexibility and control over the behavior of the hierarchy of coverable work items.

Current workaround:
Project admins continue to rely on custom issue linking instead of using the Parent field

CONTEXT & EXAMPLES:

Concrete example:
A project admin may prefer to build requirements from issue links instead of Jira's parent-child structure.

Workaround risk:

• Requires effort to maintain consistent linking between issue types
• The hierarchy may be duplicated when using the Parent-child relationship and issue linking