Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

'Parent id' option is not present in 'Link & Sub-Task' during csv import for JIRA

kowshik.x.mani@gsk.com
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 7, 2024

'Parent id' option is not present in 'Link & Sub-Task' during csv import for JIRA.

How it needs to be enabled?

 

parent-id-JIRA.jpg

2 answers

3 votes
Walter Buggenhout
Community Champion
January 7, 2024

Hi kowshik.x.mani@gsk.com and welcome to the Community!

As per the documentation in this support article, use Parent instead of parent id (navigate to the section about creating parent-child relationships.

Hope this helps!

kowshik.x.mani@gsk.com
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 7, 2024

Thanks for Suggestions. I looked into it and tried the same. Still facing issue.
Provided screenshot for more clarity on this.

kindly help me to find out if i had done any mistakes.

Issue-csv ss.PNGIssue-01.PNGIssue-02.PNG

Walter Buggenhout
Community Champion
January 7, 2024

I am not sure you need to map the issue id field while importing. But I do see that yu did not assign an issue id to your child issues, which does not comply with the requirements listed in the documentation:

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

Like Joseph Chung Yin likes this
1 vote
Joseph Chung Yin
Community Champion
January 7, 2024

kowshik.x.mani@gsk.com -

Welcome to the community.  To supplement what @Walter Buggenhout stated, please note that "Parent Link" is a special field to support issue hierarchy configuration roll-up via Advanced Roadmap for Jira.

Parent Link is for rolling up Epic issue type to the next custom higher level issue type in your env.  It is different then "Parent ID" (where it is used primary for subtask roll-up to parent issue).

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events