Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,558,746
Community Members
 
Community Events
184
Community Groups

Moving tickets from classic to next gen project doesn't fill custom fields

Mike Slivka
Mike Slivka Jan 28, 2019

We have occasion to move tickets from a classic project to a next gen project, but there is a custom field we added to the source and target issue types which doesn't fill. The field name is the same in both the projects. 

Is there a way to get custom fields to migrate between project types? 

Answer
Watch
Like Be the first to like this
391 views

1 answer

0 votes
Alexey Matveev
Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
Jan 28, 2019

Hello,

The only way I found to migrate custom fields is to export all data from a next-gen project to a csv file, then create new custom fields and modify your csv file so that values in the custom fields in the next-gen project would be named as newly created custom field. Then you can upload the csv file to Jira. 

I would strongly advise you to try it first in a test environment.

Reply

Suggest an answer

Log in or Sign up to answer
Atlassian logo
Team-managed projects
TAGS
AUG Leaders

Atlassian Community Events

See all events