unable to bulk update sub-task for task using csv import

[akshaybhange]

I am trying to update the sub-tasks created for the task using csv file via admin panel. 

I've tried multiple variations with issue key, issue id, parent. 

I get following error : 

"while updating issues have been skipped because they already exist in destination projects."

In Jira settings --> System --> Import and Export --> External System Import

my CSV headers are: 

Issue key, Summary, Issue Type, Parent, Issue id, & some custom fields

[Bill Sheboy · Accepted solution]

Hi @akshaybhange -- Welcome to the Atlassian Community!

What type of project is this: company-managed or team-managed?  You may find that information in the project list or at the bottom-left of the page expanding area when viewing the project.

There is a known defect for team-managed projects where sub-tasks cannot be updated using a CSV import.  You may watch / vote for this defect to see progress: https://jira.atlassian.com/browse/JRACLOUD-81917

Kind regards,
Bill

[akshaybhange]

Hi @Bill Sheboy , 

I checked the project, I don't see "team managed" text on the left sidebar, I guess my project is company managed. 


https://support.atlassian.com/jira-service-management-cloud/docs/how-can-i-tell-if-im-in-a-classic-and-next-gen-project/

[akshaybhange]

Thanks, I noticed It is a team managed project. 

[John Funk]

Hi @akshaybhange  - Welcome to the Atlassian Community!

Can you share the header row of your spreadsheet CSV? 

[akshaybhange]

my CSV headers are: 

Issue key, Summary, Issue Type, Parent, Issue id, & some custom fields

[John Funk]

Very good - thank you. Now, what are you trying to update for the Sub-task? 

[akshaybhange]

I'm trying to update some of the custom fields I have created for sub-tasks. 

[John Funk]

Okay - you shouldn't need the parent if you are just updating field for the Sub-task. 

Put the key of the sub-task in the Issue Key field. Leave off the Issue ID and Parent fields - you should not need them. 

[akshaybhange]

got an error, 

"None issues and projects imported.

Issue can't be created as issue type is sub-task but parent issue key or id is not specified"


Sample CSV : 
Issue key, Summary, Issue Type, custom field
KAN-2, SubtaskSummary, Subtask, customValue

[John Funk]

Oh, sorry, yes you do not need the Issue Type field either since these are just updates and not creates. 

[akshaybhange]

@John Funk didn't work 

got another error :

"Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state: Failed to remove subtasks [KAN-2] parents. A parent of a subtask cannot be removed."

[akshaybhange]

should I be using issue ID instead of Issue key.

[John Funk]

No, Issue Key is correct. Maybe it thinks you are clearing the Parent field for some reason since it is not mapped. So I try adding the Parent  column in with the existing value of the Key for the parent. 

[akshaybhange]

Got 2 issues here. if I add parent id (for eg. 10000) it is asking for issueID & Issue Type. 

If I provide both of these then it'll skip the issues. 
Feels like a loop :(

[John Funk]

The Parent should be a Key like ABC=123, not the ID. 

Can you post a screenshot of the first row of your CSV, along with the header row?

Also, can you post a screenshot of the mappings in the import tool?

[akshaybhange]

CSV: 

Issue key,Parent,Summary,Order ID,SIL SKU,Qty,Product Desc,Order Status,Courier,AWB Number,Dispatch Date,Delivered to,Delivery date
KAN-2,KAN-1,Proper Sub Task 1,1,NUPI - 1,1,Apple Iphone,Delivered,Bluedart,12345678,15-Jul-24,Person 1,18-Jul-24


Mappings: I've not included some of the custom fields which are not relevant: 

[akshaybhange]

@John Funk what could be the issue ?

[John Funk]

I don't know. I am seeing a lot of questions in Community the last few days about CSV import problems. I suggest you open a support ticket with Atlassian to see what they say. 

https://support.atlassian.com/contact/#/

Please post back here with the resolution in case someone else is having the same problem.

Good luck!

[akshaybhange]

@John Funk , thanks a lot for the help. 

I found out the project was team managed, and as @Bill Sheboy mentioned, it's a known bug. I've created another company-managed board and CSV upload is working in it.