Tasks importing as Stories?

[Laurie Hanlon]

Hi,

I am using the CSV importer to import issues to a new project.  I did a test run into a Classic Project and everything worked fine.  Ideally I need a next gen project so created my new project as next gen with the Scrum template.  All my issues imported successfully but when I check them in the project they were ALL imported with the issue type = Story.  My CSV file has both Story and Task issues, and the same data worked fine in a Classic Project.

Any ideas?  I was manually able to change the issue type from Story to Task in the UI so I know Task is valid for this project.

Thanks, Laurie

[Petter Gonçalves]

Hello Laurie,

Welcome to Atlassian Community.

JIRA Next-gen uses different issue types than Classic projects, although they have the same name. This might cause the wrong mapping of the issue type when importing them by CSV and using the Issue type name.

This bug is reported here:

- External System Import to Classic Projects using CSV adds Next-Gen Issue Type to Scheme

To effectively fix the problem, please open an internal ticket with Atlassian support:

https://support.atlassian.com/contact

To avoid it while the fix is implemented, an existing workaround is to import the CSV file using the issue type's IDs instead of their "Names". This can be gathered by going to Jira Settings > Issues > Issue Types and click Edit next to the issue type. The ID will be displayed on the URL.

Let me know if this information helps.

[Laurie Hanlon]

Thanks for the response!  The bug you noted is for issue types not importing correctly into a classic project.  In my case the import to a classic project worked, but NOT the import the Next Gen project.  It was the Next Gen project where all the Issue Types were Story.  Will the suggested workaround still work when importing to a Next Gen (are the issue type ID's the same in Next Gen as in Classic?)

[Petter Gonçalves]

Hello Laurie,

Indeed, the bug is related to a Classic project import, however, the same behavior happens in Next-gen too.

By the way, the Issue Type IDs are different in both Classic and Next-gen project, so the mentioned workaround should work for you.

To get the Issue ID of next-gen issue types, you can navigate to the project settings > Issue Types > Click in the issue type. The ID will be displayed at the end of the URL.

Please, let me know when you have the chance to try it.

[Laurie Hanlon]

Unfortunately, that did not work. They all imported as Stories again.  I did discover that the Issue Type ID will be different for EVERY project, so at first I got errors that the ID's already existed.  I had grabbed the ID's, then deleted my Project and created a new one with the same name, not realizing the ID's would be diff.

After figured that out, on a fresh project (no issues yet), I got the issue type id's, then did the import, but again they still all imported as stories.  What is also strange is that they are importing in a strange order, not in the order of my CSV file.

[Petter Gonçalves]

Hello Laurie,

Thank you for your detailed answer.

I further investigated it internally with the details you provided and could confirm you are being impacted by a new bug, which is related to the first bug mentioned in this thread:

- As a Jira admin, during the CSV External System Import to a Next-Gen project, the mapping of the "Issue Type" value and the "Story Point Estimate" value is not respected

Initially, I was not able to reproduce the mentioned bug in my test instance, so sorry for not being able to identify it right away.

What causes the bug and the aleatory behavior in different instances (Sometimes it works, sometimes it create tasks, sometimes it create Stories) is still being investigated, but it seems that scoped fields are not getting imported at all, so it simply selects the default issue type to be created.

That being said, the best workaround I can recommend you at this moment would be to import your issues and then use the Bulk operation functionality to move the issues to a different issue type. These would be the exact steps:

1 - Import your issues through CSV

2 - navigate to your issue navigator page and run a query to return all the imported issues

3 - Click in the three dots menu >  Bulk edit all issues

4 - Select the Edit issue option > Select Change Issue type > Finish the client

Additionally, we understand how this bug might have impacted your business. We are currently working to get bugs fixed and new features implemented in this new next-gen template, so please vote and watch the vote to increase its priority and also receive notifications about the bug fixing.

Let us know if you still have any questions.