Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,465,790
Community Members
 
Community Events
176
Community Groups

Loosing fields and linked issues while moving issues from Jira Software to JPD

Hi !

I am using a Jira Software project to manage my Product Backlog and I would like to migrate it on JPD but I am loosing a lot of information while moving issues from one project to the other : 

I am using the Bulk feature to move the issue but while doing this

  • I am not able to map some native fields (description, labels) and custom fields (public description) even though I have created them in JPD with the same names (or they already exist in JPD)
  • I am losing all my linked issue doing the migration. My linked issue are the feedback and client request that are stored in another Jira work management project and it is super important that I keep those links

Is that normal ? Is there a way to bulk migrate the issues without loosing some information ?

Thanks for your help :) 

1 comment

I've had similar problems with bulk "Move". So, I've instead opted to download as CSV the data I want, then Imported as CSV to manually map the fields into the JPD project where I've created those fields.

 

One thing that I noticed when manually mapping, is that if the header of the field contains certain characters like apostrophe, or quotes, or dashes, it does not map and thus does not import correctly. So you'll need to rename the header of those columns to something generic with only letters and numbers.

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events