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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • 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

Migration from classic to next-gen - Custom fields


I tried moving issues from a classical project to a next-gen project.

We are using custom fields in the classic project and which we recreated in the next-gen project.  For fields that are option fields, checkboxes (multiple-choice) or multiple-user fields, migration asks if I want to keep the orginial values. Fields are configured the same way, i.e., same options notated for option and checkbox fields. 

However, even with activation of the check box, no values are transferred. What are we missing?





1 answer

0 votes
Jack Community Leader Dec 19, 2019

unfortunately NG projects do not support many of the features including some custom field types. A migration will result in the loss of some data and capabilities.

Suggest an answer

Log in or Sign up to answer

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