Issue types lost after bulk move?

[Brian Hann]

I decided to move our issues from a next-gen project back to our old project because next-gen is missing many features we still need.

I set up all the issue type mappings for the move, but after the bulk move was complete it looks like all of our 1000+ issues did not map correctly and are all of the type "Task".

This is extremely disheartening, and means many hours of work in order to correctly assign epic vs story vs bug types back to all the issues.

Has anyone else had this happen? Is there any chance of restoring what was lost?

[Ste Wright]

Hi @Brian Hann 

I tested this just now with Epics, Tasks and Stories and it worked fine - there was quite a lot of configuration steps for issue type, statuses and field mapping though as I went through the move.

I know this isn't useful now - but issues don't always move gracefully between Next-Gen and Classic I've found. I would usually suggest exporting the data and then re-uploading it into a Classic Project.

I don't believe there will be a method to restore the data once it has been moved - but you could still export it and make the modifications in excel, before re-uploading it.

Uploads including issue keys via the Admin Importer will update issues rather than create new ones - so you could correct the relationships between the different issue types before uploading them all in one go, rather than having to open many screens and make manual modifications.

Ste