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

Migration to JPD Types and Hierarchy

emily.scheer

I just watched the webinar and demo of new features in JPD Premium.

We have manually created a hierarchy with Opportunities and Solutions through custom fields (following a video tutorial you shared earlier). Is there a simple way to migrate to the built-in hierarchy you offer now?

Accepted answers

Tanguy Crusson_z9fqgo

Hi @emily.scheer yes you can use bulk edits to set the type of ideas (from a list view: bulk select ideas > change the type) and set connection field values (list view > bulk select ideas > set the value of a connection field)

From the FAQ:

how can I bulk edit ideas?

You can do that by selecting ideas in a list view (via the checkbox left of ideas) and changing field values there.

Demo: bulk change ideas

All comments

Tanguy Crusson_z9fqgo

From the FAQ:

how can I bulk edit ideas?

You can do that by selecting ideas in a list view (via the checkbox left of ideas) and changing field values there.

Demo: bulk change ideas

Dr_ Ankita Mehta-OpsHub_ Inc

Hi @emily.scheer

The new hierarchy features in JPD Premium definitely simplifies things. However, there are few things to consider:

Depending on how much data you’ve built up, this could be a light cleanup or a more involved effort — and during this time, teams may experience some disruption or downtime, especially if they rely heavily on filters, reports, or automations tied to the old structure
There’s no one-click migration (yet) — Jira Product Discovery doesn’t currently offer an automatic way to map your custom fields directly into the new built-in structure.
Depending on how much data you’ve built up, this could be a light reorg or a bigger lift — so worth scoping carefully.

What Teams Typically Do (But Each Has Trade-offs)

CSV export/re-import: Gets the job done, but you may lose links, comments, or formatting if not handled carefully.
Gradual transition: Some keep the old setup and use the new hierarchy for future items — but this can cause confusion or split reporting.
Manual updates: Filters, automation, and links tied to custom fields may need to be reviewed and rebuilt.

You may consider an enterprise-grade migration platform OpsHub Migration Manager(OMM) — a trusted Atlassian partner with over a decade of experience in migrations. It supports full-fidelity transfer of issues, custom fields, relationships, comments, users, and attachments with zero downtime and non-disruption— even allowing teams to continue working in the source JPD project while the migration is in progress.

Drop us line if you have any questions!:)

Tanguy Crusson_z9fqgo

Hi, I think that's partly misleading.

There's definitely no need to recreate items with the new idea type. Just bulk select all the ideas and update their type and voila.
If you use a custom field to represent hierarchical things you can simply use bulk updates to change that to use a connection field instead (Demo: bulk change ideas)

I did it for the project we use to host the roadmap for the Jira Product Discovery team where we have 4 years of data. Deciding what hierarchy to use was the most complex part. Changing the project to use it took roughly 2 hours.

Dr_ Ankita Mehta-OpsHub_ Inc

Thanks for the clarification, @Tanguy Crusson

Welcome!

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

Quick Links

Find more posts tagged with

jpd