Error finding the Parent ID
Asked by Jael Palmeiro de Carvalho:

I'm trying to import existing tasks from a issue that already exist, so, there's this error and I can't find that field "Parent Issue" too.  
I would like to know if it's a native field or it's something that i have to search on everytime i'll do the import.

The error is: "You have to define which CSV column maps to Issue Id if you want to import sub-tasks."


Answers:
author: Trudy Claspill
body: Hello [@Jael Palmeiro de Carvalho](/t5/user/viewprofilepage/user-id/5346118)

Welcome to the Atlassian community.

If you want to import subtask and add them to as children under an issue that already exists, then in your CSV file you have to include an entry for each subtask that has the issue key for the parent task to which you want to add the imported subtask.

Example:

Type,Summary,Parent  
Sub-task,Summary for my issue,ABC-123

When you execute the import you then need to map that Parent field from the CSV file to the Parent ID field.

![Screenshot 2023-10-20 at 4.12.05 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/287549i902E72115EE70F25/image-size/large?v=v2&px=999 "Screenshot 2023-10-20 at 4.12.05 PM.png")

comments: author: Jael Palmeiro de Carvalho
body: Thanks, that solved my first problem, but now they request an issue ID (red line on the top):  
![image_720.png](https://community.atlassian.com/t5/image/serverpage/image-id/287718i01239EBBE9806A27/image-size/large?v=v2&px=999 "image_720.png")![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/287722i68C9F008B13BD1C5/image-size/large?v=v2&px=999 "image.png")


author: Trudy Claspill
body: Yes, that is correct. That is stated at the bottom of the screen.

![Screenshot 2023-10-23 at 1.22.49 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/287809i5DA75F81DB486B5E/image-size/large?v=v2&px=999 "Screenshot 2023-10-23 at 1.22.49 PM.png")

You just need to add another field/column to your CSV file to contain a unique number for Issue ID for each sub-task. Just a number; it doesn't have to match an issue key.


author: FINA ALFI KHASANAH
body: but i can't find parent id field when maping subtask, how can i configurate this?


author: Trudy Claspill
body: [@FINA ALFI KHASANAH](/t5/user/viewprofilepage/user-id/5399448)

Welcome to the Atlassian community.

The Jira product has changed since the answer was written.

Review the message at the bottom of the import field mapping screen:
>
> #### Child-parent relationships {#toc-hId-293147801}
>
> To import child-parent relationships, define the column mapping for: Issue Id, Parent and Issue Type

The Parent ID field is no longer in use. Now you need to use the Parent field.


author: Brian Franklin
body: [@Trudy Claspill](/t5/user/viewprofilepage/user-id/3569011)

But what goes in the parent field now??

Below is my import template from before (when I used Parent ID). Now it gives an error even when I use "parent" instead.

CSV:

|------------|----------|-----------|--------------|----------|------------|-----------|---------------|----------|--------|--------|------------------------|
| Issue Type | Issue ID | Parent ID | Summary      | Priority | Start Date | Due Date  | Complete Date | Assignee | Sprint | Status | Description            |
| Story      | 1        |           | Story 1      | High     |            | 19-Jan-24 |               |          | 732    |        | Description of story   |
| Subtask    | 2        | 1         | Subtask 1.2  |          |            | 19-Jan-24 |               |          | 732    |        | Description of subtask |
| Subtask    | 3        | 1         | Subtask 1.33 |          |            | 19-Jan-24 |               |          | 732    |        | Description of subtask |
| Story      | 4        |           | Story 4      | Highest  |            | 19-Jan-24 |               |          | 732    |        | Description of story   |
| Subtask    | 5        | 4         | Subtask 4.5  |          |            | 19-Jan-24 |               |          | 732    |        | Description of subtask |
| Subtask    | 6        | 4         | Subtask4.6   |          |            | 19-Jan-24 |               |          | 732    |        | Description of subtask |
| Story      | 7        |           | Story 7      | Low      |            | 19-Jan-24 |               |          | 732    |        | Description of story   |

* Subtask 'Subtask 1.2' doesn't have a valid Parent selection during the validate phase. Issue may not be created.
* Subtask 'Subtask 1.33' doesn't have a valid Parent selection during the validate phase. Issue may not be created.
* Subtask 'Subtask 4.5' doesn't have a valid Parent selection during the validate phase. Issue may not be created.
* Subtask 'Subtask4.6' doesn't have a valid Parent selection during the validate phase. Issue may not be created.

I tried pre-creating the stories so they would have issue-keys and tried using those. Got same errors:

|------------|----------|-----------|---------|----------|------------|-----------|---------------|----------|--------|--------|------------------------|
| Issue Type | Issue ID | Parent ID | Summary | Priority | Start Date | Due Date  | Complete Date | Assignee | Sprint | Status | Description            |
| Story      | CFP-9206 |           | Story 1 | High     |            | 19-Jan-24 |               |          | 732    |        | Description of story   |
| Subtask    | 2        | CFP-9206  | Subtask 1.2       ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |
| Subtask    | 3        | CFP-9206  | Subtask 1.33      ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |
| Story      | CFP-9207 |           | Story 4 | Highest  |            | 19-Jan-24 |               |          | 732    |        | Description of story   |
| Subtask    | 5        | CFP-9207  | Subtask 4.5       ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |
| Subtask    | 6        | CFP-9207  | Subtask4.6        ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |

Tried using the Story Issue ID. Same results:

|------------|----------|-----------|---------|----------|------------|-----------|---------------|----------|--------|--------|------------------------|
| Issue Type | Issue ID | Parent ID | Summary | Priority | Start Date | Due Date  | Complete Date | Assignee | Sprint | Status | Description            |
| Story      | 121456   |           | Story 1 | High     |            | 19-Jan-24 |               |          | 732    |        | Description of story   |
| Subtask    | 2        | 121456    | Subtask 1.2       ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |
| Subtask    | 3        | 121456    | Subtask 1.33      ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |
| Story      | 121457   |           | Story 4 | Highest  |            | 19-Jan-24 |               |          | 732    |        | Description of story   |
| Subtask    | 5        | 121457    | Subtask 4.5       ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |
| Subtask    | 6        | 121457    | Subtask4.6        ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |

Tried without the stories actually in the import file. This "worked".

|------------|----------|-----------|---------|----------|------------|-----------|---------------|----------|--------|--------|---|---|---|
| Issue Type | Issue ID | Parent ID | Summary | Priority | Start Date | Due Date  | Complete Date | Assignee | Sprint | Status | Description ||   |
| Subtask    | 2        | 121456    | Subtask 1.2       ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |||
| Subtask    | 3        | 121456    | Subtask 1.33      ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |||
| Subtask    | 5        | 121457    | Subtask 4.5       ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |||
| Subtask    | 6        | 121457    | Subtask4.6        ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |||
| Subtask    | 8        | 121458    | Subtask 7.8       ||            | 19-Jan-24 |               |          | 732    |        | Description of subtask |||

This "worked" but now something that I could do all in one file I have to do separately. Create the stories/tasks. Run a report to get the actual Issue-ID number, put that number for all the specific subtasks, AND remove the stories.

Is there a way to do all this in one CSV anymore (like before, understanding the # per CSV limit)?

I am importing over 2000 subtasks over 15-20 stories/tasks each month, so this is going to be ++**EXTREMELY**++cumbersome.


author: Trudy Claspill
body: [@Brian Franklin](/t5/user/viewprofilepage/user-id/5210542)

Given that the original poster already accepted an Answer for their post, please start a new Question in the forum. You can include in it a link to this post if your think this post is relevant.

In your new Question in addition to the information you provided above, please tell us the Type of project into which you are trying to import data - Software, Business/Work Management, or Service Management, and Team Managed or Company Managed. Also show us the field mappings screen you are using when you import the issues.


Tags: cloud

jira-work-management-cloud