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; } } }

Migrating to JPD (from Jira delivery project) and Child tickets

Michael Mackuliak

Hi team,

Context: Our Organization has recently moved from Data Center to Cloud and the Product team is adopting JPD. We were using a regular Jira project (called "Product Board") to manage our work (ideas). We would link, as children tickets, out to delivery tickets that were in another project for developers, let's call it "Dev Board".

I'm moving the product team's tickets from "Product Board" into JPD. When I do this the children tickets are dropped. So I have to keep a list of what the children tickets were and then manually re-link them as delivery tickets.

I'm hoping there is some better way - have a few hundred tickets to move and some product tickets are linked to two dozen delivery tickets.

Accepted answers

Jeny Stoeva

Hi @Michael Mackuliak ,

You can do a CSV export on the issues in your Product Board Project (the links are also exported) and then CSV import to the new JPD Project and map the links as well so they are preserved. t will also allow you to map other fields. Have you tried that and do you know how to do it?
You can access both export and import to CSV from the Filters > All issues view.
Just try with 1-2 tickets to figure out how to mappings work and then you can do it for all tickets.

All comments

Michael Mackuliak

Also surprised (disappointed) that I can't migrate data into global fields. The ticket have a field called "Level" - I've also set up a global field in JPD called "Level". Being able to map the two is not an option during the move process.

I suspect maybe if I did a CVS import some of this would work but I need links from the product project preserved. When I move them all links persist which is great and necessary, also no duplication with a move.

Jeny Stoeva

Hi @Michael Mackuliak ,

Michael Mackuliak

Hi Jeny - Thank you for the idea, I was going to try it but seems I can only export as XML - which import doesn't support.

My concern with this approach is that I will have duplicate tickets, the one in the Product Board and then the new one created from the import.

Michael Mackuliak

Figured out how to do the export in CSV. Children tickets are not listed in that export

Jeny Stoeva

@Michael Mackuliak , You were saying that you have tickets in one project linked to tickets in another project and those links are preserved when you export the tickets to CSV, I just tried it and below is an example how the links look like in the export. Also the links within the project are preserved.

I am not sure I understand your concern about the duplicate tickets since you anyway want to move away from the Product Board, from what I got, and this whole export/import exercise is about moving everything in the JPD project.

You should do the full CSV export. Screenshot 2024-10-31 at 11.39.14.png Screenshot 2024-10-31 at 11.35.58.png