When creating a Sub-Defect in a Test Run, the Parent Issue dropdown should display issues of Epic and Story type

Description

When creating a Sub-Defect in a Test Run, the Parent Issue dropdown should display issues of Epic and Story type.

User friction

• Allowing Sub-Defects to be linked to Epic or Story issues helps prevent users from selecting incorrect issue types.
• Currently, when creating a Sub-Defect in a Test Run, any issue type can be selected as the Parent Issue.
• This flexibility can lead to inaccurate associations, resulting in incorrect data and misleading results.

Steps to reproduce (right now) / Actual Result:

• Create a Test and associate it with a Test Execution
• Execute the Test
• From the Test Run, create a Sub-Defect
• Observe that any issue type can be selected as the Parent Issue by entering its issue key

IMPACT

What would improve if solved:

• Prevents users from selecting not desired Parent Issue types when creating Sub-Defects
• Ensures Sub-Defects are consistently linked only to valid Epic and Story issues.
• Improves data accuracy and reporting reliability
• Reduces user confusion and rework caused by incorrect issue associations.
• Creates a more guided and error-proof Test Run workflow

Impact on stakeholders:

• Fewer errors when linking Sub-Defects, reducing rework.

Current workaround:

• Manually write the desired Issue Key and select it.

CONTEXT & EXAMPLES:

Concrete example:

• A user creates a Sub-Defect during a Test Run and accidentally links it to a Task instead of an Epic or Story. This mislink causes the developer to miss the defect in the Epic or Story context, leading to delayed fixes and inaccurate test reports. Restricting the Parent Issue dropdown to Epic or Story issues would prevent this error.

Workaround risk:

• Manually ensuring Sub-Defects link to Epic or Story issues relies on user diligence, increasing the chance of mistakes, inconsistent data, and inaccurate reporting.