Summary

When we use the Sprint name in the CSV import file, the import is completed without the Sprint field being populated and the below warning message is shown.

This article outlines the steps to populate the Sprint field when an issue is created/updated using the CSV import.

Environment

.
Jira Cloud

Cause

The CSV import expects the sprint ID to be used in the CSV file instead of the sprint name. Two different sprints can have the same name, as mentioned in this community article and the feature request, JSWCLOUD-15634.  Therefore, the system uses the unique identifier, Sprint ID.

An attempt to use the sprint name in the CSV file will result in the above warning message, and the import is completed without the sprint field being populated.

Solution

Sprint column in the CSV file

To avoid this warning message and to ensure that the Sprint field is populated during the import, we can use the Sprint ID in our CSV file. Below is the sample format of the CSV file:

How to find the Sprint ID

A sprint can have duplicate names.  Each sprint is associated to a project board.  Make sure you pick the sprint associated to the correct project board and its ID.

Option 1: Using the issue search

1. Go to "Search Issues" in Jira (Basic search).
2. Click More and add the "Sprint" filter.
3. Select the required sprint name. (Just below the Sprint Name, you can see the Board Name where the sprint originated. This is helpful in case you have multiple sprints with the same name).
   
4. Click JQL on the far right to switch the JQL search mode.
5. Here you can make a note of the sprint ID.

Option 2: From the issue view

Open any issue from the Sprint, and hover the cursor on the Sprint Name.

The Sprint ID is displayed at the bottom left corner of the browser window.