Parent ID (Which is now "Parent") is not importing properly

[Brian Franklin]

Referencing: https://community.atlassian.com/t5/forums/editpage/board-id/jira-work-management-questions/message-id/10136

I am trying to import my software project into Jira.  I am using the same template that I have used for over a year, and it would seem that sometime in NOV or DEC 2023, the PARENT-ID field was changed to just "PARENT".  Now my projects will not import.  I have changed the import mapping to Parent for the parent ID in my CSV.

I "think" we have team managed since different people have admin to different projects.

Here is the mapping screenshot:

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:

• 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.

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:

• 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.

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, in multiple steps.  If this is the way it works now, I will have to create the stories/tasks, run a report to get the actual Issue-ID number for the stories /tasks, put that number for the parent of all the specific subtasks (without the stories in the same file for reference),  

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.

[Trudy Claspill]

Hello @Brian Franklin 

You can find the project type from the Type column on the View all projects page under the Projects menu.

I was successful creating both the parent issues and subtasks with this very simple CSV

Issue type	Issue ID	Parent ID	Summary
Task	1		Story Summary
Sub-task	2	1	Subtask 1
Sub-task	3	1	Subtask 2
Task	4		Story 2
Sub-task	5	4	Subtask 3
Sub-task	6	4	Subtask 4

My field mapping screen looked like this:

Notice that the only field that has the Map field value column checked is Issue Type.

When I clicked Next on the above screen I got another screen listing the values I had in my Issue Type field, and showing pull-down lists for me to select the actual issue type in the destination project to which those correlated.

I notice that in your field mapping screen several fields, including the Issue ID and Parent fields, are checked in the Map field value column. I recommend that you make sure those two fields are unchecked in that column, use simple sequential numbers in the Issue ID column in your CSV, and try the import again.

The only fields that should have the Map option checked are fields where you are mapping to a selection list type of field, I believe.

[Ashley Luchtenberg]

I find I am running into the same problem. This does not happen when I import using the "Import issues from CSV" from the Issues screen in a project but I can't map to Original Estimate with that. As an admin to our team-managed project I have access to the External System Import that allows me to attach the hours but it will not link the Epics to the Tasks as Parents. I know an update was just put out and have seen the Confluence page from that detailing how to use it, but it is not working for me. Any help would be greatly appreciated.