I have the below CSV in a file, and I want to preserve the values of 'Issue Key', 'Status' and 'Resolution' when I import. How do I do that? I can't find a way to map 'Issue Key', 'Status' or 'Resolution' into JIRA without JIRA automatically assigning a new 'Issue Key', 'Status' is 'TO DO', and 'Resolution' to 'Unresolved'. I'm using 'atlassian-jira-software-7.3.1-standalone'
Issue Key,Component,Fix Versions,Layer,Summary,Description,Assignee,Reporter,Issue Type,Priority,Status,Resolution ABC-135,appserver,201701,Data,foo,foo,user1,user1,Enhancement,High,Done,Rejected ABC-140,aws,201701,Presentation,foobar,foobar,user1,user1,Discrepancy,Medium,In Progress,Unresolved ABC-139,web portal,201701,Logic,bar,bar,user1,user1,Requirement,Low,Done,Completed
It's this problem https://confluence.atlassian.com/jirakb/missing-fields-to-map-during-import-issues-to-csv-operation-720420577.html and the 'Solution' doesn't work
Hi @Haisam Ido,
There are two ways to import CSV in JIRA
1) Under the issues section - "Import issues from CSV"
2) Under external system import (requires admin rights)
If you use the second option(admin rights) you will see fields like Status, Assignee, Resolution etc which are not available if you try to import via the first option.
Similar question here - https://answers.atlassian.com/questions/9866203
Status and resolution must exist in JIRA for you to be able to map them.
Have you got Rejected and Completed resolutions in Admin -> Resolutions? And the three status under admin -> status?
For status, the status must also be used by workflows for the issue types you have mapped for the issues
Key will not be imported, it is generated by JIRA according to the project you are importing it into. If you specifiy and map a key in an import, then the import is treated as an update to an existing issue.
I have same problem. I would like to update existing Jira tickets with values in a CSV file, but it is not possible to map the Issue Key (though in the atlassian documentation, it is mentioned it is possible: https://confluence.atlassian.com/adminjiraserver071/importing-data-from-csv-802592885.html).
+1 Alec - long story short, you cannot update issues using the "Import Issues from CSV" under the Issue menu if you're not a since you cannot map the key field. Basically you can only create new issues using that function. The documentation needs to be updated, and I would recommend adding this ability via the "Import Issues from CSV" routine.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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!
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