nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Import from CSV - Cannot map epic issue type

Jakub Zděblo

I want to import issues from CSV file. I map issue type as epic but issue always map as tasks.

Here are screenshots:

After import there is no warning.

But when I look to my project roadmap there are no new epics, just tasks in a backlog.

Thanks for your help.

Accepted answers

Petter Gonçalves

Hello @Jakub Zděblo

Welcome to Atlassian Community!

Checking the details and screenshots you provided, I believe you are trying to import Epics to a Next-gen Project in Jira. Is that correct?

If I got it right, you might be facing the following bug with Jira application:

- NextGen - CSV Import - Failed to assign Epic as IssueType

Feel free to vote and watch the bug to increase its priority and also receive notifications about its fix implementation.

As a workaround, you can import the Epic issues into a new Classic Jira project and then move the issues from the Classic project to your Next-gen by following the steps in the documentation below:

- Migrate between next-gen and classic projects

Let us know if you have any questions.

All comments

Petter Gonçalves

Hello @Jakub Zděblo

Welcome to Atlassian Community!

Checking the details and screenshots you provided, I believe you are trying to import Epics to a Next-gen Project in Jira. Is that correct?

If I got it right, you might be facing the following bug with Jira application:

- NextGen - CSV Import - Failed to assign Epic as IssueType

Feel free to vote and watch the bug to increase its priority and also receive notifications about its fix implementation.

As a workaround, you can import the Epic issues into a new Classic Jira project and then move the issues from the Classic project to your Next-gen by following the steps in the documentation below:

- Migrate between next-gen and classic projects

Let us know if you have any questions.

Jakub Zděblo

Hello @Petter Gonçalves

thanks for quick response. That is correct, thank for information regarding the bug.

Actually I just noticed that the import works correctly if you do it through creating issue card and not through Jira settings and External system import.

Procedure is the same but there is little difference in the beginning. First choosing file and in the next step choosing encoding. So I suspect that you have two different implementations and one is correct.

Patricia Francezi_iDev_

@Petter Gonçalves - i have read the migrate b projects article, but could not figure how will be managed the subtasks created in next-gen, then moved to classic.

Will they loose info as the epics?

Patricia Francezi_iDev_

Hello all

I run this article yesterday, and there was an improvement in the process, but its not reflected in the article.

I have provided feedback on the article itself, but follow here, may be it would help another Admin

Yesterday I used this article for migration from a Next-gen project to a classic.
The Epics: the article says it will loose the link between issues, but it linked perfectly, I just need to change the Epic Name, as Next-Gen doesnt have this field. It uses the summary. The summray is kept in the Epic Issue.
The Story Points: Article says it will be lost, but it was migrated without problems.
The labels: article does not mention that will be lost, but it was lost.

I think that as you seen to improved the data migration, you should considering improve the reports calculation or showing the sprint report at least, as the Sprint information goes with project and its issues.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud