CSV Import Issues

I am trying to import issues. I am able to create them . I have entered assignee name in CVS but /when file is imported and fields are mapped, issues are not assigned to that user, also th/ere is another problem related to date format. I have used m/d/yyy format and when i entered 8/17/2014 in csv , the month it showed was January. Need urgent response please.

2 answers

1 accepted

0 votes

Are the users valid assignees for the project you are importing the data into?

Yes, like my own user that i am using is a valid one. I can always assign any issue to my user.

what is recommended to use for assignee (username or user id)? , please respond. I am using User Name instead of user id.

Furthermore, If I add components e.g. Core Component , New Requirement in CSV file and these components are not already created in the system, will CSV import process create these new components for me or I have to create them first? same goes for versions, labels.


Also please tell If I enter same issue id, how jira tackels it . (Why I am keeping same id as in our case , we are just creating stories that have same number and assigned to different teams. We are not going granular to create sub tasks and link them with the stories).

Look forward to your kind response.

It should not matter if you use user name or user ID if you tick the "map value" box on import.

If you do NOT map the users, then you must use the exact user ID that they have have in Jira - their login, and exactly as it is in the user list - case sensitive etc.

CSV can create components, versions and other fields.

However, if you enter an issue ID, Jira will treat it as an UPDATE to the existing issue

For sub-tasks, you can enter a field for "parent" if you already have created the parent issues in Jira and know what they are. Or, if not, then you can a column for "parent ID" and put in a unique ID for the parent issue and re-use it on the sub-tasks to indicate who they belong to. It's critical that you get your issue type column right in the CSV here as well.

Hi issues are imported now but i can not see the workflow buttons with issue. I have set the status field as Open. My workflow starts from To Do -in dev- in test- done-close. Is there anything else I should include in csv so that I can see the workflow action buttons and can perform transitions in the workflow. urgent response required please.

You set the status of the issues to "open" in the import, but that is not a valid state in your workflow? Is that correct?

You'll need to either do the import again with a valid status, or change your workflow to include "open", with transtions to where they should be, move them through to the right status and delete the old open status.

I have imported the file with the right status according to my workflow and it is working great . Thank you for your prompt response. One more query regarding original estimate . How does jira treat this format. Like if i enter 720 is this hour, minute or seconds?

I am able to figure this out. It captures estimates in seconds. I am left with two of the problem areas after import. 1 - all the issues show creation date of today when i imported issues whereas my sprint started back date. does system allow me to log work in back dates ? secondly i want to see a burn down chart that has effort that has original estimates (total hours of all the issues as per orginal estimate) and a line o f remaining hours ( that should reflect total remaining effort). Is it possible i can do this in jira?

1. You needed to set the creation date in the CSV, or it uses "now" because that is genuinely when the issue was created! You can log work in the past though, that's not an issue.

2. I'm not sure I understand this, but let's start with the obvious question - do you have Jira Agile installed?

great for the point 1. I will create another CSV that will have only creation date values and Issue ID. Can I use these two columns only to import

on second point , yes we are using jira agile and it is on demand.

I have tried creation date and it worked superb for me Nic. Also burn down chart curve can be viewed hours on the y axis starting from the maximum value and I believe it will go down , as the team keep burning hours and logging works against their issue items assigned. Please correct me If my understanding on burndown is not correct. Thanks.

1. See https://confluence.atlassian.com/display/JIRA/Importing+Data+from+CSVand look for "updating existing issues" - I'm not sure it will work for the created date though

2. Ok, so you have standard burndown charts as described. As long as you put the sprint data in.

Good, I wasn't 100% sure it would work on creation date, not tried it.

You are correct about the burndown chart, it will burn down as you log work and resolve stuff.

Don't forget about case.

Please use M/d/yyy

Thanks for the feedback. What about Assignee issue. I logged with my own user (having administrator privileges) and assigned the items to my user but assignee is still blank.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,963 views 12 18
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot