The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
Export Issue Comments from Cloud
Following Atlassian documentation for migration practices, I am trying to convert all the Nex-Gen Projects in Cloud to Classic Software Projects as I cannot import Next-Gen Projects to an on-prem instance.
Epic Name, Epic Link, and Next-Gen specific Fields appear to not be able to move from Next-Gen to Classic using the Bulk-Tool.
It seems since these Fields either do not apply to Next-Gen or apply only too Next-Gen, moving these issues with these data points into the global configuration will cause data loss no matter what I do.
Is it possible to export the Fields mentioned above accurately for Next-Gen Issues? If this could be possible along with Comment Bodies (all comments is very important), I could use our on-prem import tool to create these issues in the Target instance.
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.