Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to import csv in x-ray

a611145
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 15, 2019

Hi,

Problem: I'm trying to import the csv file in X-Ray Jira with all the mapping field required. But I'm not able to import the file and it throws an error as below:

Import completed with 4 errors:

Error importing issue [externalId='autoid-343909961-1', summary='a']
Error importing issue [externalId='autoid-553514000-2', summary='b']
Error importing issue [externalId='autoid-444502446-3', summary='c']
Error importing issue [externalId='autoid-1453643362-', summary='null']

I'm creating .csv file on my local machine and copying it to the terminal server as I can access JIRA on the terminal server. But on the terminal server, csv files are converted into the LibreOffice csv file format as Microsoft office is not present there.

 

csv import error.pngerror log.pngfile format on terminal server.pngPlease help me to resolve this issue.

 

1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 18, 2019

This error in the stacktrace is telling:

Status [ To Do ] does not have a linked step in the [ Xray workflow with new ] workflow. Please map to a different status.

This means that the specific issues in Jira you are trying to import here are mapped first to a project and then to an issuetype.  Each issue type in a project can have a different workflow.  Given the values of your import, we know that workflow is called 'Xray workflow with new'.   That specific workflow does not have the To Do status in it.  Hence Jira won't let you import issues of that type, to that project, with that specific status.

There are two different approaches here to work around this:

  1. Change the CSV file to use a different status other than To Do for these issues
  2. OR  Change the workflow to include the To Do status in that specific workflow.

Either approach should let you get past this problem, however #2 requires you to be an administrator of the project in order to change the workflow.

If you're not sure which statuses are valid for this issue type of that project, one way to find this would be to first create/locate an issue of that type in that project, then go to that issue.  On the issue details view there is a link to 'View Workflow'.  This is one way to see what valid statuses exist for that issuetype in that project.

Suggest an answer

Log in or Sign up to answer