Set Bug/Defect as the Default and Only Issue Type for "Add Defect" in Test Runs

Description

In Xray Cloud, when using the Add Defect option from a Test Run, users can select and link any available Jira work item type. This can lead to inconsistencies where non-defect issue types (e.g., Story, Task, Epic) are linked as defects.

The request is to provide a configuration option that allows administrators to:

Restrict the available issue types to a specific defect issue type (e.g., Bug/Defect) when using Add Defect.
Optionally set a default issue type that is automatically preselected when creating a defect from a Test Run.

User friction
Users expect the Add Defect action to create or link actual defect records. The ability to select unrelated issue types introduces confusion, increases the likelihood of user error, and impacts defect reporting accuracy.

Steps to reproduce (right now) / Actual Result:

• Open a Test Execution and navigate to a Test Run.
• Click Add Defect.
• Choose to create or link an existing issue.
• Observe that multiple Jira issue types are available for selection.

Actual Result:
Any permitted Jira issue type can be selected and linked as a defect.

Expected Result:
Only designated defect issue types (e.g., Bug/Defect) should be available, or administrators should be able to configure which issue types are permitted.

IMPACT
The current behavior allows non-defect work items to be associated as defects, resulting in inaccurate defect tracking, reporting, and traceability.
What would improve if solved:

• Consistent defect management across projects.
• Improved data quality and reporting accuracy.
• Reduced user mistakes during defect creation and linking.
• Stronger alignment between Jira issue taxonomy and testing workflows.

Impact on stakeholders:
This would improve usability, reporting accuracy, defect visibility, and process governance by ensuring only valid defect issue types can be linked from Test Runs.
Current workaround:

Users must manually select the correct defect issue type and rely on project guidelines or training to avoid linking inappropriate work item types.

Context & Examples:

Many organizations use dedicated issue types such as Bug, Defect, or Incident for defect management. Allowing all issue types to be linked through the Add Defect action can create inconsistencies in reporting and traceability.

Concrete example:

A tester discovers a failure during execution and clicks Add Defect. Instead of creating a Bug, a Task is accidentally linked. The issue is then counted as a defect in the test run context, while not being tracked as a defect in project reporting, causing discrepancies.

Workaround risk:
Reliance on user discipline and process documentation does not prevent accidental misuse. As project size and user count grow, the risk of incorrect issue classification increases, leading to inaccurate reporting and additional administrative effort to identify and correct mislinked issues.