Creating work items in different spaces using csv importer

Question

Has anyone here successfully imported work items in a space that's mentioned in csv? The article documents support for this https://support.atlassian.com/jira-software-cloud/docs/create-issues-using-the-csv-importer/ but it hasn't worked for me. When I provide Space Name and Space Key fields in csv, I don't know how to map them in the mapping step since Jira doesn't have such native fields available for mapping to. And when I don't map them, they don't get used. Also, the wizard asks for the target space and it's a required field. When selected, the importer creates all work items in that same one space.

Note: we are using Atlassian Jira cloud.

Here is my csv:

Summary,Description,Work Type,Space Name,Space,Space Key,Assignee,Flow Item Type
Test ticket,Test desc,Epic,IIGK TEST,IIGKTEST12,IIGKTEST12,,Debt

Trudy P Claspill · Answer

@Dalvi,Amit

Another aspect to this is that you must be a Jira Admin in order to use the option to specify the Space within the CSV data. If you are not a Jira Admin you will be required to specify a single Space into which the data will be imported.

To use this feature the Jira Admin would execute the import by clicking the gear icon near their avatar in the upper right and selecting System.

Then they would select External System Import.

Then "switch to the old experience"

Then they would select "CSV" and select the file to import.

Then the option is available to specify that the destination Space is included in the CSV.

Arkadiusz Wroblewski · Answer

Hello @Dalvi,Amit

Space Name and Space Key are not normal Jira fields that you would map like Summary or Description. They are special CSV import columns for telling Jira which space the work item should go to.

So I would keep those column names exactly as Atlassian expects them and not try to remap them to something else.

Alternatively Try @Trudy P Claspill Advice with small portion of Data.

If Jira still forces you to pick one target space in the wizard and then imports everything there, then that is the part I would question. In that case, I would test with a very small CSV first, just to confirm the actual behavior.

If it still does not split the items into the different spaces from the CSV, then I would treat that as current importer limitation/behavior and use separate imports per space as workaround.

Trudy P Claspill · Answer

Hello @Dalvi,Amit

Welcome to the Atlassian community.

Atlassian has been implementing a terminology change. Spaces were previously called Projects. Not everything has been updated yet.

Try mapping Space Key and Space Name to Project Key and Project Name, respectively.

(Disclaimer: I have not actually tested an import with this mapping.)