The inability to hide Create Sub-Defect may result in accidental sub-defect creation.

Description

Provide a project-level configuration option in Xray Cloud to hide or disable the "Create Sub-Defect" action from the Test Run screen and test step defect menu, while keeping "Create Defect" and "Add Defects" available.

User friction

Organizations that use standard Jira Bug issues for defect management want to prevent testers from creating sub-task defects accidentally. Even when only Bug is configured in Xray Defect Mapping and no sub-task issue types are intended for defect tracking, the Create Sub-Defect option remains visible, causing confusion and incorrect issue creation.

Steps to reproduce (right now) / Actual Result:

• Configure Xray Defect Mapping in a project to include only Bug as a defect issue type.
• Ensure no sub-task issue type is mapped as a defect.
• Execute a Test and open the Test Run screen.
• Navigate to a test step and open the Defects menu.

Actual Result: The Create Sub-Defect option is still displayed alongside Create Defect and Add Defects.
IMPACT

• Testers may create defects using an issue type that is not part of the organization's defect management process.
• Additional administrative effort is required to identify and correct incorrectly created issues.
• User confusion regarding which defect creation option should be used.
• Inconsistent defect tracking and reporting across teams.
  What would improve if solved:
• Organizations could enforce defect management standards directly within Xray.
• Reduced risk of accidental sub-task defect creation.
• Cleaner user experience by showing only relevant actions.
• Improved process governance and reporting consistency.
  Impact on stakeholders:
  Testers, test managers, and project administrators experience increased risk of incorrect defect creation, resulting in additional effort to maintain consistent defect tracking and reporting.
  Current workaround:
• Instruct users to always select Create Defect instead of Create Sub-Defect.
• Provide user training and documentation explaining the correct defect creation process.
• Periodically review created defects and correct issues that were created as sub-defects.
  CONTEXT & EXAMPLES:
  Many organizations standardize on Jira Bug issues for all defect tracking and intentionally do not use Jira sub-task defects. However, because the Create Sub-Defect option remains available in the Test Run UI, users can still select it even though it is not part of the intended workflow.
  Concrete example:
  A project configures only Bug as its defect type and requires all defects to be reported in a centralized defect backlog. During execution, a tester clicks Defects > Create Sub-Defect instead of Create Defect, creating a sub-task under an unrelated parent issue. The defect is then excluded from the team's normal defect management process and requires manual correction.
  Workaround risk:
  The current workaround relies entirely on user awareness and training. Human error remains possible, particularly for new or occasional users. This can lead to inconsistent defect creation, increased administrative overhead, and inaccurate reporting.