Hello... Jira Cloud here.
I am working with a few folks on moving their issues over from NextGen to Classic Projects.
What I am wondering is if there are any work arounds to resolve the issues named in this link under
Specifically - the links between Epics and Stories that are broken when moved to Classic.
Right now I am trying to determine resource and effort for these and just want to get a good idea if what Atlassian states cannot be done in the above link, actually cannot be done.
i haven't done this but since Epics in NG don't have Epic Link (or has this changed :-)), I would assume the following to be the right (?) approach....
And as an additional safety net: create a csv export of your issues with all custom fields before you start moving anything at all. That way you have a snapshot of your data before you move them as a reference for fixing anything that may go wrong or that you need to fix manually (such as the story point estimation).
@JohnI put the wrong link in - in this link it mentions the issue of Epics and Links
yep. that is precisely to the point i made...
<<<<<<<< SNIP >>>>>>>>
@John I put the wrong link in - in this link it mentions the issue of Epics and Links
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events