Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Copy ALL JIRA Cloud "Next Gen" Custom field values into labels field for ALL individual JIRA issues Edited

We are in process of migrating from "Next Gen" Projects to classic project in JIRA cloud. This is being done because want to migrate to Data Centre and cannot have any "Next Gen" Projects in existance for this to be under taken. Currently if we were to just move the "next Gen" project to "Classic" project all of the custom fields that have been set up are lost. We would like to retain this information and rather than a heavy manual data entry task it has been deemed acceptable if we could convert those custom fields into the single native labels field.

Is this possible or is there a better way to retain this information?

1 answer

0 votes

Hello @Darren Fairweather

Welcome to the Atlassian Community!

I believe the best way to transition your issues from a Next-gen to a Classic board keeping the custom fields would be by exporting and importing the next-gen issues to a Classic project using CSV format. These would be the steps:

  1. Export your Next-gen issues by creating a query and using the option Export Excel CSV (All fields):
    Screen Shot 2020-10-07 at 20.59.32.png
  2. Edit the CSV file:
    1. Set the Custom field names as labels
    2. Change the project fields to the correct classic project
    3. Remove the Issuekey and Issue ID
    4. Check if workflow statuses or issuetypes must be changed (Mainly Subtasks, that must be changed to Sub-tasks)
  3. Import the CSV file to your site

Let us know if you have any questions.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

326 views 9 7
Read article

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