moving issues from one project to another project

[Hoc]

Hello,

I want to move issues from one project to another.

I've recreated the same fields on my new project but when I try and move its telling me to enter new values for the fields? I thought that if the fields have the same names it should be able to detect it automatically and copy it over?

I noticed that its also showing fields that shouldnt even be on the issuetype?

Any ideas?

Thanks!

[Ollie Guan · Accepted solution]

Hi @Hoc ,

What kind of situation?

• classic project to next-gen
• classic project to classic
• next-gen project to classic
• next-gen project to next-gen

[Hoc]

Hey Olllie,

from next-gen to next-gen.

I also tried to use the 'retain' option and that didn't work either.

[Ollie Guan]

As far as I know, in next-gen projects, custom fields are completely independent, and you can regard them as different fields.So you need to manually match them during the migration.

[Jack Brickey]

Correct

[Hoc]

Hello,

What did u mean manually match them? As in manually set the value fora each field for each issue?

Thank you

[Krister Broman _Advania_]

Since you are mentioning recreating the fields i will assume that you are working with at least one next-gen project. 

Next gen projects are not a good way to work in if you need to move issues between projects. Most data will not transfer between projects and will not be recreated see.   

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

So expect this data to get lost when you migrate between projects:

• Custom fields
• Story points estimation
• Reports
• Report history
• Parallel sprints
• Project and issue keys
• Versions and releases