Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Importing Sub-Tasks via CSV

We have JIRA Core - Server.  I need to move sub-tasks from 1 project to another.  I export the sub-tasks via CSV, made the adjustments to Parent ID and Issue ID, and used the CSV import tool.  I receive an error that the Parent ID is invalid and none of my sub-tasks will import.  So I created a 'test' sub-task in said Issue.  I exported and found that the Parent ID matches PERFECTLY.  I cannot find much documentation in the Atlassian 7.3 for importing sub-tasks (older documentation discusses it, but their screens have obviously changed since then). 

How are you importing sub-tasks correctly with the Parent ID?

2 answers

0 votes
Brant Schroeder Community Leader May 25, 2017

Chelsea,

  If you are just moving the tasks from one project to another I would suggest using a bulk change and migrating them.  If the tasks need to remain in the old project and you have to create them in the new project you will need to make sure that the following is defined for each sub-task:

  • Issue Id
  • Parent Id
  • Issue Type

If any of the three items are missing you will get an error and they will not import.  

An example would be:

Issue ID, Parent ID, Summary, Issue Type
001, ASD-01, This is Sub Task One, Sub-Task
002, ASD-01, This is a Sub Task Two, Sub-Task
003, ASD-01, This is a Sub Task Three, Sub-Task

The issue ID must be unique to the imort file, the parent ID must match an issue in the JIRA project.

If you use the format I provided you should be good to go.

Thanks
Brant

 

Be aware that import engine uses External Issue ID, not internal ID from the issue url

where do you find the External Issue ID?

You can try to edit the jira ticket to assign a unique value to External Issue ID then use that unique value as Parent ID during importing. Hope this can help!

I tried doing this sub-task thing, but it's showing me that Parent ID not found. Even though I have the exact issue number in Jira to match. 

Why is that?

 

try using key value for Parant Id. Hope this helps

2019-03-28_11h34_35.png

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

322 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you