nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to move the Custom Field info From Next Gen to Classic projects?

Prabhu Chilukuri

Hi Team,

I have tried to move the Next Gen Issues to Classic project. But not able to move the custom field info to Classic. I have created the custom fields same as in Next Gen projects.

Please kindly assist in this issue,

PFB Screenshot for your reference,

next Gen Custom Field issues.png

Accepted answers

John Funk

Hi Prabhu,

This is not possible - custom fields created in Next-gen project are only available for that project and cannot be shared or "moved" to other projects. You have to create a new custom field to be used in other projects.

However, if you have a shared custom field outside of Next-gen projects, it can be used with multiple Classic Software, JSM, or Business type projects

All comments

Guilhem Dupuy

Hello @Prabhu Chilukuri ,

Normally if you go to the next step, you should have the opportunity to map these fields with your new custom fields in your classic project don't you ?

Trudy P Claspill

I work strictly with Classic projects rather than next-gen, but from my research it appears that you may not be able to move data in custom fields in next gen projects to classic projects using the Move option.

See this post: https://community.atlassian.com/t5/Jira-Software-questions/How-to-convert-quot-next-gen-quot-project-to-quot-classic-quot/qaq-p/933703

Prabhu Chilukuri

HI Guilhem,

Thanks for the Reply,

There was no option to map the Custom fields.

John Funk

Hi Prabhu,

However, if you have a shared custom field outside of Next-gen projects, it can be used with multiple Classic Software, JSM, or Business type projects

PRABHU naidu

Hi John,

Thanks for the info,

FYI, I've already created the custom fields outside of Next gen. Seems like there no option to move the custom fields data to classic directly.

Guilhem Dupuy

Another option would be to export the issues of your next-gen project in an Excel of CSV file, and then re-import it in the classic Jira project.

This should allow you to make sure that your old fields are mapped to the correct new fields

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud