The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
You need two additional columns in your CSV.
One for a unique identifier for each issue you are importing (not a Jira issue key, just unique within the CSV) and a second one that you'll map to "parent issue", which, for each sub-task, contains the unique identifier of the parent issue you're importing.
Hi @Nic Brough _Adaptavist_ ,
Thanks for your reply.
I have the below sheet as csv
Issue Type | Epic Name | Summary | Status | Description | Issue Id | Parent Id |
Epic | Diagnostics : Implement Visteon Manufacturing specific diagnostics functionalities | Parent Epic - [JLR CCCM] : CarPlay : WiFi Disconnection | No Specs | Parent Epic - description | 102 | |
Story | Diagnostics : Implement Visteon Manufacturing specific diagnostics functionalities | story - Summary | No Specs | story - Description | 102 | |
I am trying the import the same, Issues are newly created properly but I can't get the parent child linkage between the two.
kindly someone help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, so you're talking about the Epic : Story relationship, not story : subtask
Your import is failing because
1) you are trying to put an Epic name on a Story. The field does not exist for story-level issues, you can only put an Epic name on Epics
2) you have told it that one of your stories has a parent issue. Stories are not sub-tasks, they don't have that parent/child relationship
The language people use here is unclear and confusing on a technical level - we often talk about "parent child" relationships in the hierarchy interchangably, but they are different things in the code and data.
Take, for example, a typical hierarchy in Jira:
Initiative is a parent of Epics, the Epic is a parent of Stories, the Stories are a parent of sub-tasks.
But in Jira's code and data,
All of those can be described as "parent/child", but they're all totally different structures.
To make a story belong to an Epic, you need to set its Epic Link to the name of the Epic you want it to belong to.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.