As a user, I need Xray TestRun Step attachments to be preserved even when Test Step attachments are deleted till we choose Reset or Merge operation.

Description

Currently, when a step-level attachment is deleted from a Test, the corresponding attachment reference in existing Test Runs also becomes unavailable. Although the attachment link remains visible on the Test Run page, attempting to access it results in an error because the underlying attachment has been removed.

This behavior differs from Xray Server/DC and may lead to the loss of historical evidence associated with executed tests. Test Run data is generally expected to represent the state of the test at execution time and should remain unchanged unless the user explicitly chooses to update the execution using Reset or Merge actions.

User friction

Users expect historical execution records, including step attachments available at the time of execution, to remain accessible within Test Runs.

When a step attachment is removed from the Test definition, users do not anticipate historical Test Runs being affected, especially when the Test Run has not been Reset or Merged

The current behavior creates confusion because attachment links continue to appear in the Test Run, but fail when opened.

Steps to reproduce (right now) / Actual Result:

• Create a Manual Test with one or more step-level attachments.
• Execute the Test and create a Test Run.
• Verify that the step attachment is available in the Test Run.
• Navigate back to the Test definition.
• Delete the step-level attachment from the Test.
• Open the existing Test Run.
• Attempt to access the attachment from the Test Run.

Actual Result:

• The attachment entry/link is still displayed in the Test Run.
• Opening the attachment results in an error because the source attachment has been deleted.
  

IMPACT

What would improve if solved:

• Preserves historical execution integrity.
• Aligns Test Run behavior with execution auditability expectations.
• Prevents loss of execution evidence.
• Reduces confusion caused by broken attachment links.
• Provides consistency with Server/DC behavior.
  **

Impact on stakeholders:
Testers

• Can reliably access historical evidence attached to executed test runs.

QA Leads/Auditors

• Maintain traceability and audit records for completed test executions.

Organizations in Regulated Environments

• Can preserve execution artifacts required for compliance and auditing purposes.

Support Teams

• Fewer customer questions and incidents regarding missing or broken Test Run attachments.

Current workaround:
There is currently no practical workaround to preserve the historical attachment once it has been deleted from the Test definition. Users must avoid deleting step attachments if they need to retain access to them from existing Test Runs.

CONTEXT & EXAMPLES:

Concrete example:
A tester executes a Test containing a screenshot attached to Step 1 as supporting evidence.

Months later, the Test is updated and the original attachment is removed because it is no longer relevant to the test definition.

When reviewing the historical Test Execution, users expect the original screenshot to remain available because it was part of the execution context at the time the test was run. Instead, the attachment link remains visible but produces an error.

Workaround risk:

• Historical evidence may be lost unintentionally.
• Broken attachment links create uncertainty about data integrity.
• Teams may be forced to keep outdated attachments in Test definitions indefinitely to preserve Test Run history.
• Potential compliance and audit risks where execution artifacts are required to remain immutable.