Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Xray import JUnit results from tests but it creates different test issues



I am trying to import the results of my test plan execution to Xray, but I have some troubles. I list you the steps that I follow to reproduce it:

  1. I create test Cucumber issues that I export after this for its development in my project. I get all the tags of the stories covered with them and the test plan where I collect them.
  2. After completing them, I generate a JUnit XML report.
  3. I import it to Xray.
    • The results are imported to the correct Test Execution and Test Plan, but the test issues are not updated with the execution results.
    • Other test issues are created as "Generic" with the name "(Epic name): (name of the original test issue)" and the original test issues are not modified. Finally, I get the same amount of new test issues than the original ones that I tested.

Could you help me with this problem?



3 answers

2 accepted

0 votes
Answer accepted

Hi @Azahara Camacho

For guidance, you can check our support documentation regarding this topic: 

If your doubts remain, I recommend you to reach out Xray support and the team will be glad to help you out.

Best Regards,



Solution Architect and Testing Advocate @Xray

Personal blog on testing, Agile, and software development:

Follow me on Twitter:

0 votes
Answer accepted

Hi, This is Ashok Dalabehera. I am also facing the exact problem.

Hi @Ashok Dalabehera - Ending up in the exact same scenario of duplicate test issues being created. Ours is a custom junit xml and trying to figure out what is being missed. Any hints on how this issue was resolved at your end? Thank You.

0 votes
Stefan Salzl Community Leader Mar 08, 2022

@Azahara Camacho , @Srinivasan Anantharaman , @Ashok Dalabehera :

Is there still an issue with this?


@Stefan Salzl 

Adapting a workaround process by mapping “issuekey” field during upload to avoid  duplicate issues being created. Requires jira-admin rights :) 

Stefan Salzl Community Leader Mar 11, 2022

that sounds interesting. Would you mind to describe the workaround here?


Not sure if yours is the same use case. Anyways, Please refer the solution to 

Solved: Generic tests from automated code (Xray) updated c... (

Note: Updated the link. 


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events