Row limitation in the Xray Test Case Importer

[Claudio Antonacci]

When importing the CSV, Jira/Xray processes up to 55 rows without any issues. As soon as the file contains 56 rows, the importer misclassifies one of the step rows as a separate issue. Since step rows do not contain a Summary field, this leads to summary='null' and the import fails. The test cases themselves are created correctly, but the importer aborts during step creation once the total number of rows exceeds this limit.

[Marc -Devoteam-]

Hi @Claudio Antonacci 

This is probably related to a misconfiguration in your CSV file.

Can you provide file details (screenshots)?

[Claudio Antonacci]

Unfortunately, I cannot upload any data; our system does not allow it.

But the fields are:

Laufnummer

TCID

Zusammenfassung

Beschreibung

Status

Autor

Bearbeiter

Repository

Komponenten

Prio

Aktion 

Daten

Erwartetes Erbebnis

We are working with the German version.

[Marc -Devoteam-]

Hi @Claudio Antonacci 

Is this a test case and the above are all stepes within that test case?

Is there no hidden row in your csv file or is the previous row missing a field or comma to specify that field to be empty?

The issue will be in your csv.

[Claudio Antonacci]

These are the fields of the CSV input.

Please note that the "Laufnummer" is not required; it is only used as an internal reference.

[Marc -Devoteam-]

Hi @Claudio Antonacci 

For my perspective what are you importing Jira issues or Test cases?

Within using the Jira default importer, a summary is always required on each row.

If you just want to import test cases with manual steps you should use the Xray Test Case importer

Jira issue import, https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/ 

Xray Test case import (test with maual steps), https://docs.getxray.app/space/XRAY/301695197/Importing+Manual+Tests+using+Test+Case+Importer 

[Claudio Antonacci]

These test cases are created in an Excel file using this structure, then converted into a CSV and uploaded to Xray via the Jira Test Case Importer. This process triggers the error. However, the test cases are still created in Xray, which makes the error difficult to understand. Since I am not the one creating the test cases, I need to have them verified to ensure they are correct. At least I can find all the test steps that are present in the Excel file.

[Marc -Devoteam-]

HI @Claudio Antonacci 

Are you creating test cases and some where you directly want to import the manual steps on the created Test?

If so you need to use the Xray Teat Case importer, as the Jira default importer can't work with lines that don't have a summary, as this is mandatory in the Jira CSV importer

[Claudio Antonacci]

Hello Marc,

Yes, I am importing the test cases using the Test Case Importer, and all the test cases, including the steps, are there. However, I am receiving this message, and I cannot interpret or understand what it means.

If I have 55 test steps in the CSV file, the import works without any error message. But if I have 56 test steps, all the test steps are still imported, but I receive this error message with the exact same CSV file (except for the number of test steps).

For me, it’s not clear from the JSON what this is supposed to mean. Even Copilot doesn’t provide a proper explanation, which is why I am reaching out to the community.

[Marc -Devoteam-]

Hi @Claudio Antonacci 

The error means that there is a summary column in your csv that has no value, where it should have one.

So there is some kind of issue on your CSV.

What if you create a new file and use the inforamtion?

[Claudio Antonacci]

Hi Marc,

I came to the same conclusion and did some testing, but the behavior is very strange.

I have 4 test cases with between 4 and 30 test steps each. If I leave out any one of the test cases, everything works fine — it doesn't matter which one I exclude.

The same applies at the test step level: when I reduce the total number of test steps from 56 to 55 by deleting a single step, the process works correctly. Again, it makes no difference which specific step I remove.

What is particularly puzzling is that even when the error message appears, the result in Xray seems to be correct. All test cases and all test steps are present and appear to have been imported successfully.

Based on this behavior, it is very unlikely that the issue is related to the CSV format itself

Do you have any idea what could be causing this behavior?

Best regards,
Claudio

[Marc -Devoteam-]

H @Claudio Antonacci 

No I have not, also I can't find any on this in the documentation.

You might want to contact Xblend support (Xray) on this.

https://jira.getxray.app/servicedesk/customer/portal/2 

[Claudio Antonacci]

Thank you very much for your assistance and engagement. I will reach out to Xray Support directly to discuss this matter further.