Create hierarchy of Ideas in Jira Discovery

[Matteo Nicolich]

We use Jira Discovery to mature into Initiatives. Initiatives might be big and we split them in incremental value delivery we call Product Goals.

Since we use Jira Discovery also to communicate roadmap and roadmap execution statues I would like to create hierarchy between Ideas.

Initiative are composed by multiple Product Goals. 
Need help for:
- I would love to have a parent / child link option in Ideas
- I would love to see them Grouped graphically in the Timeline View

[Dirk Lachowski · Accepted solution]

It’s about to be added, see https://community.atlassian.com/t5/Jira-Product-Discovery-articles/A-giant-update-for-hierarchies-issue-types-opportunity-solution/ba-p/2893631

[Tanguy Crusson]

Yep! In the meantime, this is what you can do. From the FAQ:

Can we create different issue types and their relationships? (e.g. parent/child or opportunity/solution)

Not yet, but it's on the roadmap and we're working on it right now. In the meantime you can use the flexible fields and views system to do this. Here is an example:

Demo: grouping solutions by opportunities. And here's a recording of how to reproduce this configuration

[Tanguy Crusson · Accepted solution]

Hi there: you can now start creating custom product hierarchies (e.g. Opportunities-Solutions, parent-child and more) using a feature from the Jira Product Discovery Premium plan. 

About the feature:

• Custom product hierarchies

About the JPD Premium plan:

• JPD Premium landing page (to sign-up)
• JPD Premium FAQ
• JPD Premium implementation guide

[Tanguy Crusson · Accepted solution]

Hi there: you can now try this feature as part of the JPD Premium plan, which launched (silently 🤫) last week.

• JPD Premium landing page (to sign-up)
• JPD Premium FAQ
• JPD Premium implementation guide (including details how to create hierarchies)

[Matteo Nicolich]

Hello! 

We jumped on it. We are just figuring out the best configuration.

First step we moved the classification we had as custom Field into distinct Types

Now we'll build connections.

Those guides are very useful. I'm now wondering if it would be better to split into multiple projects but we just onboarded a lot of users including exec's and changing again can hurt adoption and understanding of Views

[Tanguy Crusson]

That's awesome. If you use global fields, moving ideas between projects should be a relatively easy exercise (and you'll keep all connections between ideas). It's usually best to start with a small number of projects though (keep it as simple as possible for as long as you can 🙂)