How can I get lost issues while migrating from next-gen to classic project type?

[Deepak Sharma]

I was using next-gen project type for my project. I moved the issues from next-gen to classic project type successfully but I got to know there were some loss of data as follows,

• All the epics are migrated but the linked issues were lost
• Story points of all the issues were lost

Is there a way to get the lost data back?

I am using Jira clouds.

Any help will be highly appreciated

Thank you! 

[Alexey Matveev]

Hello,

You should have read the guide for migrating next-gen to classic. It is written there that:

• Active sprints: Sprints in progress in your classic project won't move to your next-gen project. Issues that were in the active sprint in your classic project will be in the backlog of your next-gen project.

• Epic links and issue links: Any issue links in your classic project will not exist in your next-gen project. The issues themselves will still exist, but the links between them won't.

• Subtasks: All subtasks will be lost in this migration process.

• Custom fields: These must be recreated in your new next-gen project.

• Story points estimation: This data will be lost, however you'll be able to start using story points estimation by enabling the Estimation feature in your next-gen project.

• Reports: Data for your project's Velocity report won't be saved. The Velocity report will show that no points were completed in past sprints.

Right now you can only restore a backup to another cloud (if you have a backup) and restore everything manually.

[Deepak Sharma]

Thanks for answering my question but this is more about classic to next-gen and I moved from next-gen to classic. 

Is still there any way to get backup of the lost data?

Thank you!

[Alexey Matveev]

If you did not take a backup before moving, then you can not have the backup. If you do bulk changes in Jira, it is always a good thing to take a backup before it.