As a User, I can choose if the Parent issues linked to Requirements show linked in Defects

Description
When a Defect is created during a Test Run execution, Xray automatically links it only to the issue that is directly covered by the Test (for example, a Story or other requirement). It does not create links to parent issues in the Jira hierarchy (such as an Epic).

Although traceability is preserved through Jira's parent-child relationships and reports continue to work correctly, the parent issues are not visible in the Defect's Issue Links section. Customers would like the option to automatically create these direct links for improved visibility and navigation.

User friction
Users navigating from a Defect cannot immediately see all related business-level issues (such as the Epic) from the Issue Links panel. They must navigate through the linked Story to understand the full context or manually create the additional links.

Steps to reproduce (right now) / Actual Result:

• Create an Epic.
• Create a Story and associate it with the Epic using Jira's parent relationship.
• Create a Test and link it to the Story.
• Execute the Test.
• Create a Defect from the Test Run.

Actual Result
The Defect is linked to the Story (the directly covered issue).
The Epic does not appear in the Defect's Issue Links.

IMPACT
The impact is primarily on usability and navigation rather than traceability. Users reviewing a Defect cannot immediately identify all related issues from the Defect itself, particularly the parent Epic.

What would improve if solved:
Allow an optional configuration to automatically create direct links between newly created Defects and parent issues (such as Epics) in addition to the directly covered issue.

This would improve navigation and make all relevant issues immediately visible from the Defect without affecting existing traceability behavior.

Impact on stakeholders:

• QA engineers can navigate from a Defect to all relevant issues more quickly.
• Developers gain immediate visibility into the higher-level feature or Epic impacted by the Defect.
• Project managers and product owners can review Defects with greater context directly from the Issue Links section.

Current workaround:
Manually create links between the Defect and the desired parent issue(s) after the Defect is created.

CONTEXT & EXAMPLES:
Current behavior is intentional: Defects are linked only to the issue they directly cover. Traceability and reporting remain intact because Jira's hierarchy can still be traversed through the linked child issue.

The requested enhancement is to improve visibility and navigation by optionally exposing parent issues as direct links on the Defect.

Concrete example:
Hierarchy:
Epic: User Authentication
Story: Login with MFA
Test: Verify MFA login flow

Current behavior:
✅ Defect → Story
Story → Epic (via Jira hierarchy)

Requested behavior:
✅ Defect → Story
✅ Defect → Epic (optional automatic link)

This would make the Epic immediately visible in the Defect's Issue Links while preserving the existing traceability model.

Workaround risk:
There is no risk to traceability or reporting, as these continue to function correctly through the existing Jira hierarchy. The drawback is increased manual effort and a less convenient navigation experience, since users must either traverse the hierarchy or manually create the additional links.