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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • 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

moving issues from one project to another project

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!

2 answers

1 vote

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

Hey Olllie,

from next-gen to next-gen.

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

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.

Like # people like this
Jack Community Leader Sep 18, 2020

Correct

Like Nic Brough _Adaptavist_ likes this

Hello,

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

 

Thank you

0 votes

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

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

227 views 1 6
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