XRay logs are removed from test run when its status is changed

[Charo Carracedo]

Description:
We are using Xray to store the results of automated testing executed through Jenkins, utilizing the Xray REST API for integration.

The test results are correctly saved to a Test Execution issue type in Xray. However, we have identified a critical issue:

• When the test run status is changed to BLOCKED, all associated logs and evidence  are removed.
• This also occurs when the status is changed to any value other than BLOCKED.

Evidences:

I could provide snapshots to better understanding

Important Notes:

• This issue only occurs when results are submitted via the API.
• When test executions are performed manually through the Xray UI, the evidence is retained correctly.
• We have reproduced this behavior in multiple scenarios, and it appears to be consistently linked to evidence saved as "Result 1".

Request:
Could you please provide more information on this behavior?

• Is this a known issue or a limitation of the API?
• Are there any recommended workarounds or configuration changes to prevent the loss of evidence when updating test run statuses?

Thank you for your support.

[Francisco Fonseca _Xray_]

Hi @Charo Carracedo

When test results are imported via the Xray REST API, the entire content of the test run (status, steps, evidence, logs, etc.) is treated as a snapshot of the execution state at that moment.

This means:

• Any manual update to the Test Run (changing status to BLOCKED) overwrites the prior automated content.
• The evidence associated with the Test Run (Result 1) is replaced or removed, because Xray assumes the latest source of truth is the manual update and not part of the test automation pipeline.

This behavior is intentionally by design.

Did I understood your question correctly? In case you need you can also reach out to our support: https://jira.getxray.app/servicedesk/customer/portal/2

Best,
Francisco

[Rosario Carracedo Riol]

Thanks for your explanation. So, we are adapting our processes to this behaviour. Sorry for the late response