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

What is the best way to merge multiple JPD projects into one?

Omer Meshar_0f60qw

We decided we want to get all the product managers into a single JPD project (we currently have a project per main product).

What is the best way to go ahead and do this? By moving the ideas from the current projects to the new merged one? By exporting and importing the ideas?

Any other way to do it?

Accepted answers

All comments

Hermance NDounga

Hi Omer,

The two ways you describes are indeed the only ways, and I would say that they can either be suitable according to your use case, but none is perfect cause they have limitations.

Moving ideas: The "Move" feature does not retain the values for team managed projects. As Jira Product Discovery projects are all team-managed projects, your ideas will arrive in the new project without values, besides description, assignee, created date and reporter. However with this method you will keep the Insights, and delivery tickets
The export/import is keeping the values, but the ideas are all newly created (so you cannot really know what are the old ones and what are the new ones) and the insights aren't kept.

So basically, if at the moment, you have a lot of insights and delivery tickets linked, and you don't want to loose them, I would recommand to use the "Move" function - especially if the values/fields of the old project do not really match the new project and will need to be reassessed.

If you barely have no insights/delivery tickets, then export/import is quicker.

I would personally do an hybrid version of it, where you export your old project, so you have the values easily accessible, then you Move the ideas to the new project, so they don't loose their insights and metadata, and then I would refer to the exported file to manually update the values in the custom fields - but that would surely take more time.

Best Regards,
Hermance
Product Manager @ Jira Product Discovery

Omer Meshar_0f60qw

Thanks Hermance.

Is there any plan to make this less painful?

Omer Meshar_0f60qw

Oh, and would moving the ideas and importing them, and then merging them would work?

Hermance NDounga

We will be exploring better solution to move ideas in the future, yes.

Oh! The merging solution would indeed be an awesome alternative to my "hybrid" idea. So you'd select the imported issue, merge it with the moved issue and keep the values and desc from the imported one. And the insights and delivery items of the moved ones will appear under the imported one!

Screenshot 2023-05-24 at 14.59.06.png

I downside I see is that until you finish this process, you'll have all ideas in double, so you need to make sure people don't change the one that later will be archived.

I also think that it will be tedious to find the two corresponding ideas, you'd need to create a new view that contains only the imported and moved ideas (not too sure based on which metadata you could filter the other ones from that view) and sort this view by summary (alphabetical order) so the corresponding one is directly below (so you can see its issue key to make sure the target idea is the right one) .

Welcome!

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

Quick Links

Find more posts tagged with

merge

team-managed-projects