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

Your Points Tracker
  • 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
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?
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

Missing fields when Importing CSV (epics, story points estimate, sprints)


Our development process usually starts with the PM writting all the stories and tasks on an Excel or Google Sheet in order to be able to include Story point estimates, divide all those stories among epics and define a sprint plan.

I've imported the csv file asigning each item to the correct field in JIRA for a next gen board I had previously created.

I don't get an error message but, onlye these fields are imported correctly:
1.- Summary

2.- Description

3.- Assignee

(all of them are uploaded as Stories)

On the other hand, this are missing:
1.- Story point estimate

2.- Issue type

3.- Epic Name
4.- Sprint

(I double checked and all those fields are part of Issue types "Story" and "Task"). I also tried exporting a CSV with the list including the "Issue key" to see if I was able to update them but still I have the same problem.

I hope someone can give me an idea of what I am doing wrong cause completing each task individually is going to be a huge waste of time.



2 answers

0 votes

Hello @matias.hilaire ,

Currently the fields you noted will not work on next-gen project types for a csv import.

Check out this previous post that was answered by one of my associates that goes into much greater detail on this, but primarily focuses on the workarounds in the BUG :


0 votes

Hello @matias.hilaire

Thank you for reaching out.

Indeed, Jira Next-gen has some limitations regarding CSV imports. In fact, the behavior of ignoring the fields you mentioned was already reported as improvement requests and we are currently working to get this fixed:

- As a Jira admin, during the CSV External System Import to a Next-Gen project, the mapping of the "Issue Type" value and the "Story Point Estimate" value is not respected 

Ability to import issues with parent-child(epic-task) relationship to next-gen project 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

About the Sprint field that is not being mapped, can you please confirm if the Sprint described is created in your project? 

As a workaround for those issues, I recommend you to use a Classic project to receive the CSV information until we have a more efficient CSV mapping for next-gen.

Let us know if you have any questions.

This just makes me angry.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

1,199 views 10 14
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