Xray should support Forge app custom fields on Defect Issue creation dialog

Description

Customers using Forge-based Jira custom fields can successfully create and manage Bugs/other isssues directly through Jira's native Create Issue dialog, where the Forge custom fields are displayed and supported.

However, when creating a Defect from within Xray Test Runs Detils page, the same Forge custom fields are not supported in the Defect creation dialog. Forge custom fields are a supported capability in Jira Cloud issue creation experiences, but appear to be unsupported in Xray's Defect creation flow.

This creates inconsistent behavior between Jira-native issue creation and Xray-driven defect creation, leading to incomplete defect records and additional manual effort for users.

User friction

• Users expect the same fields to be available regardless of whether a Bug/Defect is created from Jira or Xray.
• Mandatory Forge custom fields may be unavailable during Defect creation.
• Users must manually edit the created Defect after creation to populate missing information.
• Causes confusion because the same issue type behaves differently depending on the creation entry point.
  Steps to reproduce (right now) / Actual Result:
• Install or configure a Jira Cloud Forge app that provides one or more custom fields.
• Add the Forge custom field to the Bug/Defect issue type.
• Create a Bug using Jira's native Create button.
• Verify that the Forge custom field is displayed.
• Navigate to Xray Cloud and create a Defect from a Test Run/Test Execution.
• Observe the fields available in the Xray Defect creation dialog.
  Actual Result: The Forge custom field is not displayed or cannot be populated from the Xray Defect creation dialog, despite being available when creating the same issue type directly in Jira
   
  IMPACT
  Organizations adopting Atlassian Forge apps cannot fully leverage their custom fields when defects are created through Xray Cloud workflows.
  What would improve if solved:
• Consistent user experience between Jira and Xray issue creation.
• Better adoption of Forge-based solutions in Jira Cloud.
• Reduced manual updates after Defect creation.
• Better data quality and compliance with required field policies.
• Improved integration between Xray Cloud and the Atlassian Cloud ecosystem.
  Impact on stakeholders:
  Testers
• Can create complete defect records without additional edits.

QA Managers

• Receive more accurate and standardized defect data.

Jira Administrators

• Can implement Forge-based customizations without worrying about Xray compatibility gaps.

Developers

• Gain access to all required defect information immediately upon creation.
  Current workaround:

1. Create the Defect from Xray Cloud.
2. Open the newly created Defect in Jira.
3. Manually populate the Forge custom fields.
4. Save the issue.

Alternatively, create the Bug directly in Jira and then associate it with Xray artifacts where applicable.

CONTEXT & EXAMPLES:
Atlassian Forge allows apps to create custom fields that are supported in Jira issue creation experiences when the appropriate create/edit experiences are configured. However, support for Forge custom fields is not universal across all third-party app experiences and integrations.

This request seeks parity between Jira's native Create Issue experience and Xray Cloud's Defect creation experience.

Concrete example:
A customer uses a Forge-based custom field called "Root Cause Category" that is mandatory for all Bug issues.

• Creating a Bug via Jira → Create displays the field and allows values to be entered.
• Creating the same Bug as a Defect from Xray Cloud does not display the field.

As a result, the defect is created without required business information and must be updated manually afterward.

Workaround risk:

• Increased manual effort and reduced productivity.
• Higher risk of incomplete or inconsistent defect data.
• Potential failure of downstream reporting and automation that depend on Forge custom field values.
• User perception that Xray Cloud does not fully support Jira Cloud customizations.