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