I have a problem importing a .CSV file to JIRA. With this import i want to create new projects and new issues. Furthermore i want to keep their structure, this means i want to create subtasks and links between tasks and/or subtasks.
For creating subtasks I need two fields Issue ID and Parent ID. Issue ID should be filled, iff the issue is not a subtask. But i have subtasks that are linked to others and therefore need the ID, how should my CSV import file look?
Has anyone encountered the same problem and/or is able to help me?
You'll want to include an Issue ID for every issue that will be linked to (including Sub-tasks) and a field for each issue link type (see How to Import Issue Links from a CSV File) and then map those link fields during import.
Save the .txt configuration file when you're finished, in case you need to go through the process again.
The Issue IDs specified in your CV will then show up in JIRA as 'External Issue ID'.
Here's a sample:
|Project Type||Project Name||Project Key||IssueType||Summary||Description||FixVersion||FixVersion||FixVersion||Issue ID||Parent ID||Priority||Story points||Status||Original Estimate||Remaining Estimate||Time Spent||Reporter||Assignee||Link Breaks||Link Relates to||Epic name||Epic link||Due Date||Date Created|
|software||Chiropteran Reconcilements||CHR||Epic||Build a whimperingly anomalous angledozer||We need to build a whimperingly anomalous angledozer because the shareholders insist on it.||1||Critical||Open||Humberto Campbell||Aki Frank||anomalousangledozer568||2016.07.20 04:07:43|
|software||Chiropteran Reconcilements||CHR||Story||Rope swing into water||As an innocent bystander it would be great to rope swing into water in order to enlighten users as to the benefits of widgetry.||2||Blocker||2||Open||Aki Frank||Pablo Stephenson||anomalousangledozer568||2016.07.20 23:07:15|
|software||Chiropteran Reconcilements||CHR||Bug||Everything breaks when I try to spherize the toroid||All versions of iOS||3||Trivial||Pablo Stephenson||6||2016.08.05 09:08:47|
|software||Chiropteran Reconcilements||CHR||Bug||Everything breaks when I try to spherize the toroid||All versions of iOS||4||Critical||Pablo Stephenson||7||2016.07.27 06:07:15|
|software||Chiropteran Reconcilements||CHR||Bug||Everything breaks when I try to spherize the toroid||All versions of iOS||5||Critical||Pablo Stephenson||8||2016.07.22 16:07:27|
|software||Chiropteran Reconcilements||CHR||Sub-task||Machicolate all failure modes such that we might internalise popularity ratings||6||2||Critical||In progress||77400||39629||37771||Pablo Stephenson||Humberto Campbell||2016.07.28 10:07:00||2016.07.21 13:07:51|
|software||Chiropteran Reconcilements||CHR||Sub-task||Demonstrate everything so that we can tabularise the user interface||7||2||Trivial||Open||81000||81000||Pablo Stephenson||Josephine Delaney||2016.08.06 18:08:26||2016.07.21 14:07:58|
|software||Chiropteran Reconcilements||CHR||Sub-task||Vaccinate a new API so that we can circularise popularity ratings||8||2||Minor||Reopened||18000||4377||13623||Pablo Stephenson||Sebastien Garrett||2016.07.31 13:07:42||2016.07.21 05:07:59|
Thank you very much for your fast reply,
but when i do it like this, i always get the error ... is not of sub-task type it will not be a sub-task of ... . What is going wrong here? But it looks like i get this error even without importing links (just parent/child stucture)
Max, at the import stage check the box to map your issue type field, and on the next screen make sure that your sub-issue types are mapped to existing sub-issues in your JIRA - I had this same problem. You might need to create sub-issue types in JIRA to map to.
The wait is over... Portfolio for Jira Server and Data Center 3.0 is now officially here! Platform releases offer Atlassian an opportunity to shift our strategy, make bold predictions about t...
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