The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Jira CSV uploader changing tasks to subtasks

Deleted user
September 29, 2023

I am trying to bulk upload issues to a team-owned software project on Jira. I have formatted my CSV in accordance with the documentation. However regardless of whether I specify my issue type as a "Task" or omit the issue type column, once I have mapped all of the (identically named) columns, on import Jira complains that as my tasks are subtasks it is going to ignore the parent id. I then have to bulk change the issue types and bulk add the parent id - all of which was in the CSV. It seems like a bug, but does anyone have any other ideas? I use the following column headers: Issue type, Summary, Parent id, Labels, Assignee

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Trudy P Claspill
Community Champion
September 29, 2023

Hello @[deleted] 

According to the following change request it is currently not possible to attach an issue as a child of an Epic when importing to a Team Managed project.

https://jira.atlassian.com/browse/JSWCLOUD-17758

When you try to map the the Parent field, the import process uses that field for specifying the Parent of a Subtask only which is why the process is changing the issues to subtasks.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events