Environment field is not automatically copied from Test Executions to Defects created from Test Runs in Xray Cloud

Description
When a Defect or Sub-Defect is created from a Test Run in Xray Cloud, the Environment field is not automatically copied from the related Test Execution. This behavior was available by default in Xray Data Center and helped maintain consistent defect data.

User friction
Users must manually populate the Environment field even though the information already exists in the Test Execution. This adds extra effort and increases the risk of missing or inaccurate data.

Steps to reproduce (right now) / Actual Result

• Create a Test Execution with an Environment value.
• Execute a test and create a Test Run.
• Create a Defect or Sub-Defect from the Test Run.
• Open the created Defect.

Actual Result:
The Environment field on the Defect/Sub-Defect is empty and is not automatically populated with the value from the associated Test Execution.

Expected Result:
The Environment field should automatically inherit the value from the related Test Execution, consistent with the behavior previously available in Xray Data Center.

IMPACT

This creates unnecessary manual work and can lead to incomplete or inconsistent defect records.

What would improve if solved

• Remove manual data entry.
• Improve defect data consistency and accuracy.
• Preserve execution context in defects.
• Align Xray Cloud with Xray Data Center behavior.

Impact on stakeholders

Testers, QA leads, developers, and project managers spend additional time managing defect data and may face reduced traceability due to missing environment information.

Current workaround
Manually update the Environment field after creating the Defect.

Context & Examples
Xray Data Center automatically copied the Environment value from the Test Execution when creating a Defect from a Test Run. Xray Cloud does not currently provide this behavior.

Concrete example
A defect created from a Test Run executed in "UAT - SAP ECC 6.0" should automatically inherit that Environment value. Currently, the field remains blank and requires manual entry.

Workaround risk
Manual updates can result in missing or incorrect environment information, reducing traceability and data quality while increasing maintenance effort.