Importing tasks from csv - cant map start date or link task to an epic?

[Simon Allen]

I am trying to import a list of tasks from CSV and am having trouble with two parts of this: -

1.) mapping the start date for the task - some tasks cannot start until a certain date, i cant find a way of mapping this, i have tried the custom fie;d 'start date' but when imported the start date on the issue / task is blank?

2.) Linking tasks to specific epics, i have a number of epics set up and in need to import tasks linked to this epic but cant seem to make it work whatever way i try (parent ID, issue ID, etc.,)

Thanks

Simon.

[Petter Gonçalves · Accepted solution]

Hello Simon,

Welcome to Atlassian Community!

Per your description, I understand you are trying to import some tasks from a CSV file with the following details:

1 - A valid value for a custom field called "Start date"

2 - Link the imported tasks to existing Epics in your site

Could you please confirm if you are importing your tasks to a Next-gen or Classic project?

If you are trying to import to a Next-gen project:

 I'm afraid that the import function does not allow the mapping of custom fields and Epics, as you can see in the bug and sub-task reported below:

CSV import will fail if Next-gen custom field is mapped 

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. As a workaround, you can import the issues to a Classic project and them migrate it to Next-gen, although the Epic links will not be retained.

If you are trying to import to a Classic Project:

1 - To make sure you are using the CSv import functionality with no restrictions, run the import client by navigating to Jira Settings > System > External System Import 

2 - Make sure the date format of the "Start date" you added in the CSV file match the one you have configured for your date picker fields under Jira settings > System > General Configuration > Advanced Settings. Also, make sure if it is a date picker or a time & date picker.

3 - The field to properly map an issue to an Epic is the Epic Link. You must add a column with that name and add the Epic key to that column to properly map it in your issues:

P.S: You can also add the Epic name to the Epic link column, however, it will not work in case you have multiple Epics with the same name. That being said, we suggest you to use the Epic Key instead.

Also, check if the Epics are already created in the Site before the import and that you can properly link issues to it manually.

Additionally, please take a look at the documentation below if you have any other questions about CSV import:

- Importing data from CSV 

Let us know if you have any questions.

[Simon Allen]

Thanks for the reply - I was trying to import to a Next Gen project...

It would be very useful to have this feature.

Simon.

[Petter Gonçalves]

Thank you for your feedback, @Simon Allen

I have added this question in an internal comment to the bug and sub-tasks provided so our developers can get more details about how this is affecting our customers.

Additionally, please feel free to provide your feedback directly in the bug and sub-task I mentioned above, also voting and watching both to increase its priority and also receive notifications about any updates.