Details
Description
Description
When the same Xray JSON results file is imported more than once into the same Test Execution/Test Run (for a data-driven Test with Iterations containing Steps), the step-level results (Status, Actual Result, Evidence, Defects) under the iterations become inconsistent or disappear entirely, both in the UI and via GraphQL. The iterations themselves are created correctly; only the per-step data is affected.
Pre-conditions
- Xray Cloud tenant
- A manual/data-driven Test with Iterations that include Step results
- The same JSON results file is imported more than once against the same Test Execution / Test Run
How to reproduce
- Import Xray JSON results into a manual Test with Iterations that have Step results (sample payload: new 1.json

- Re-import the same JSON results file into the same Test Execution / Test Run
- Open the Test Run page and inspect the Step results under the Iterations (also check via GraphQL)
- Observe that step-level results are missing or show a mix of old/new values
Actual result/Attachments
Step-level results (Status, Actual Result, Evidence, Defects) under the iterations do not appear, in both UI and GraphQL, even though the iterations themselves exist. Confirmed reproducible locally by the Base Team (Alexandre Peres, see XCC-2994) after repeated imports of the same file.
Sample JSON attached: new 1.json![]()
Reindexing does not resolve it.
Expected result
After importing (or re-importing) JSON results, the step-level results should always update consistently and show the correct, current step-level result under each iteration, with no leftover data from earlier imports.
Version
- Xray Cloud 16.6.0
Workaround
None known. Reindexing was attempted and did not resolve the issue.
Attachments
Issue Links
- duplicates
-
XCC-3158 Loading...