Moving issues from Classic Project to NextGen project

[Jim Stewart]

We have a Classic IT help desk project in which we've lumped together 4 areas - security. applications, business systems and general. We decided to break those out into their own projects and I figured I would move the issues over. I am a site admin.

Someone created the new projects as Next Gen and I wanted to move the issues over to their respective projects. However, when I go to move the issues, those projects do not come up in the pick list. I can see the projects in the All Projects list and in fact I made myself lead but I cannot see them. I created a test Classic project and that works fine.

So is it safe to assume you cannot move Classic issues over to Next Gen projects or is there another way to do it?

[Alexis Robert · Accepted solution]

Hi @Jim Stewart , 

it should be possible to move those issues, as per this documentation : https://confluence.atlassian.com/jirasoftwarecloud/migrate-from-a-next-gen-project-to-a-classic-project-957974933.html

Make sure that the issue types exist in the next gen project.

Otherwise, if somehow you can't choose your project in the bulk move, I'd suggest doing a CSV export and import back into the new project.  This page can help with the process : https://confluence.atlassian.com/jirakb/how-to-export-issue-and-comment-in-csv-with-proper-format-to-import-in-jira-741934059.html

Let me know if. this helps, 

--Alexis

[Jim Stewart]

Hmm. Yes, ok I did see that. But the projects are not showing up and so I do not want to have to spend hours either trying to see them or exporting and importing which is already enough of a nightmare. I may just re-create those as classic ones. 

[Jim Stewart]

Followup - those new NextGen projects are empty and I cannot see them. But I created a new one and it shows up. I am going to assume there was something wrong with those and recreate them all. Thanks.