Several question for importing CSV

Hi Jira community.

I have several questions about importing CSV to JIRA.

Our team is using CSV import function to create issues.
There are several problems turning out when importing JIRA.

First, about issue type.
we often want to create subtask which is under a story as parent.
Although we made a parent column and chose subtask when mapping, it comes out as a task.

Do you have any idea to fix this ?

Second is about label.
I want it to fall into the label that has already existed and there are two label that we want them to be applied to.

So on CSV we tired to put the label name like LAbel1,Label2 and "Label1","Label2".

But it always comes out as one connected label.

Do you have any idea to make them separate into two label ?

The last one is about asignees.

I want to put name of person who is assigned to do the task on CSV but it does not work.

Is there specific way to put the name on the CSV ?

1 answer

1 vote

Hi @光野　かおる

Here's you can create parent/child relationship while creating issues via CSV -

Creating parent / child relationships

You can create a hierarchy of imported issues by specifying their parent / child relationships:

Add three columns to you CSV file with the headings: “Issue ID”, “Issue type”, and “Parent”
Ensure each issue in your CSV is given a unique (sequential) number in the "Issue ID" column
Reference the unique "Issue ID" number of an issue in the “Parent” column
The parent issues must exist above the child issues in the file

Refer to CSV import parent-child mapping for more details and examples of the required mappings.

In the following example, the fourth issue will be a child of the second issue if you match the "Issue ID" and “Parent” fields in your CSV file to the corresponding Issue and Parent fields in Jira. Similarly, the second issue will be the child of the fifth issue as the “Issue ID” and “Parent” fields are matched.

IssueType, Summary, FixVersion, FixVersion, FixVersion, Component, Component, Issue ID, Parent, Reporter
Bug, "First issue", v1, , , Component1, , 1, , abcde-12345-fedcba
Story, "Second issue", v2, , , Component1, Component2, 2, 5, fedcb-12345-edcba
Bug, "Third issue", v1, v2, v3, Component1, , 3, , abcde-12345-fedcba
Sub-task, "Fourth issue", v1, v2, , Component2, , , 2, fedcb-12345-edcba
Epic, "Fifth issue", v1, v2, v3, Component1, , 5, , abcde-12345-fedcba

For labels, you can import issues with multiple labels by entering each label in a separate column.

Aggregating multiple values into single fields

You can import multiple values into a single Jira field that accepts multiple values (e.g. Fix (for) Version, Affects Version, Component, Labels). To do this, your CSV file must specify the same column name for each value you wish to import to the same field. The number of column names specified must match the maximum number of values to be aggregated into the mapped field.

In this example, the second row will create issue TT-1, while the third row will set the number of votes to 7 and add two labels, and the fourth row will change the issue summary. In the next row, issue TT-2 will be created with two labels. The last row removes labels with the <<!clear!>> special marker:

issue key,summary,votes,labels,labels
TT-1,Original summary,1,label1,label2
TT-1,,7,label-1,label-2
TT-1,Changed summary,,,
TT-2,Original summary 2,1,label-1,label-2

For assignees, the supported user types are -

email address eg(bob@example.com)
Atlassian Account ID

If you aren’t sure of your Atlassian account ID, you can log in to your Jira Could site, click on your avatar on the top-right corner of the page, and go to Profile. The last part of the URL of the Profile page is your Atlassian account ID.

For eg:https://<yoursitename>.atlassian.net/jira/people/<Your Atlassian account ID>