Can I copy next-gen issues to classic in order to keep the roadmap available in the next-gen project

[Eve Hayes]

We tried out next-gen for a new project without really understanding the limitations because we were anxious to take advantage of the Roadmap feature and were switching to KanBan.

Now our team has spent time creating the epics and creating the roadmap, but we realized too late that there is no way to version/release user stories. Additionally having the acceptance criteria field (had to create and add myself) show up on the side container rather than directly above description makes it hard to locate easily. Seeing as Acceptance Criteria is the meat of the story, I'm surprised it cannot be moved to a more prominent display in the issue.

Anyway, my question is:  Is there a way to copy issues from a next-gen project back to Classic but keep the roadmap in tact? I see where I can migrate the issues back to classic but I do not want to lose all the work the team completed on the roadmap. 

[Jack Brickey]

You could move the tasks to a Classic project and leave the epics. I have not tried this to understand the impacts to the roadmapmif any. I recommend trying some test issues first.

[Eve Hayes]

Not a bad idea, thanks! We cold reference the next-gen epic in the comments if important to the business map back to the Epics (and progress). I haven't tried the migration steps yet, but I think I can select which issues are moved over.

Will propose to the team tomorrow and test out.