Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

NextGen to Classic Migrations

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 

Things to keep in mind if you migrate from next-gen to classic

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-next-gen-and-classic-projects/

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.

 

2 answers

1 vote
John Funk Community Leader Dec 07, 2020

Hi Andy,

I don't see anything in the document that list Epics and Stories as being a problem with migrated. Have you tried a single Epic and it's Stories to see what happens?

Jack Community Leader Dec 07, 2020

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....

  1. Move the NG Epic and ensure it is clean and has the desired Epic Name. Actually, I might even consider creating a new Epic in Classic.
  2. Move over your issues and use Bulk update to add Epic Link
Like John Funk likes this

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).

Jack Community Leader Dec 07, 2020

yep. that is precisely to the point i made...

Things to keep in mind if you migrate from next-gen to classic

<<<<<<<< SNIP >>>>>>>>

  • EpicsJira moves your epics across if you map them to an epic issue type in your new project. But, you'll lose the relationship between your epics and their child issues. The child issues themselves will sill exist, but the links between them won't.

Yes so that's what I am asking in this case - is this 100% true or are there ways around this with potential 3rd party tools or maybe assistance from the vendor?

John Funk Community Leader Dec 07, 2020

Yes - you can do what Jack suggested above. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

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 ...

7,045 views 8 28
Join discussion

Community Events

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

Events near you