How to group/nest ideas?
Asked by Baptiste Picard:

How is it possible to group ideas together or even create some sub-ideas?

We have some overarching ideas and different areas of the product where it would apply or different types of solutions we could bring. I was thinking or creating "sub-ideas" but that isn't available, or at least a way to link ideas with a parent/child relationship.

thanks!

Baptiste


Answers:
author: Tanguy Crusson
body: Hi [@Baptiste Picard](/t5/user/viewprofilepage/user-id/4607851)

Jira Product Discovery doesn't support issue hierarchies yet (parent-child or other) yet - it's something we have on the roadmap though.

Depending on what you want to do exactly there might be a way to do it in the app though, because of the pretty flexible fields and views system.

[Here's a demo for that](https://www.loom.com/share/c5acafb1584740c98f6871667bac6df8)

comments: author: Tanguy Crusson
body: By the way if you want I can give you access to this project if you want to check out its configuration


author: Baptiste Picard
body: that helps a lot! thanks


author: Baptiste Picard
body: it would also be super helpful to have direct access to this project, much appreciated


author: Tanguy Crusson
body: I just re-created this project to show you how to do this from scratch:

[**Video demo**](https://www.loom.com/share/c74c8cc8e5be4daaa4498bb8d3397bcd)

I also invited you to the project (check your email) so you can have a look.


author: Kalina Lipinska
body: The demo is really great! exactly the solution I was looking for, trying to create an opportunity-solution tree-like overview in JPD.   

Still, having the option to add children will be a huge improvement, but I can already move on using this solution, tnx [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) !


author: Tanguy Crusson
body: Thanks [@Kalina Lipinska](/t5/user/viewprofilepage/user-id/1445665) ! I saw your feedback and was about to send you that.


author: Adam Thede
body: Thanks for these videos. Unfortunately, it only creates the appearance of hierarchy and is harder to maintain. I hope true hierarchy is coming soon, as I'm not sure I can justify using JPD in our org until then.


author: Chad Loiseau
body: Are there any updates on parent/child relationships being represented in Jira Product Discovery?


author: Helena Jeret-M?e
body: Are there any plans on adding the functionality to build a tree structure out of the discovery results? Like the OST by Teresa Torres.

I hate flat lists. They do nothing to to show relationships and context properly. And you did add whiteboards to confluence, so.... how hard can it be? :D


author: James Doyle
body: Hi [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) are you able to advise where the idea parent/child feature sits on your roadmap?

We have lots of ideas which sit within the same product area and this would be a really useful feature to have an overarching idea which has child idea's linked.

Many thanks, James.

comments: author: Tanguy Crusson
body: Hi [@James Doyle](/t5/user/viewprofilepage/user-id/4057876) , it's high on the priority list but we have a number of things in flight now that will take a few months to land before we can get to it.

However we're not going to build a "parent/child" solution that looks like the Jira Software one. It's going to optimize for things like "opportunity/solution" or "problem/solution" - less hierarchical, more about defining and visualizing relationships.


author: Didier Gast?
body: Hi [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312), any update on this topic?

Thank you!


author: Mike Hughes
body: Fantastic, because atm we are using the **Linked issue** feature top reflect the dependency (ie. the Opportunity issue has a Linked Issue to another Opportunity).

But in the Opportunities table in JPD, you can add a Column for **Linked issues** but it just lists the number of linked issues.

So a more "not like Jira" and as mentioned:

*... optimize for things like "opportunity/solution" or "problem/solution" - less hierarchical, more about defining and visualizing relationships.*

Sounds like a much better solution for JPD.


author: Adam Thede
body: [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) any update on this?  

While I'm eager to try this new feature, I must say that it's disappointing to hear that it's still not going to be a hierarchy, like Jira proper. I expect the new feature will be useful but will not fully resolve the organization problems that led to this request.


author: Amina Bouabdallah
body: hey James, Amina from JPD here. Have you tried creating a "Product Area" field in JPD then creating views that group by Product Area? if so, what pain points remain with solutions and what did you feel blocked from doing?

Thanks!


author: Natechawin Suthison
body: Hi [@Amina Bouabdallah](/t5/user/viewprofilepage/user-id/5343033) ,  

My pain point is that,

1. I want to describe or document the product area (or fields). Currently, I need to link the details of that product area or opportunity (or field) into another documentation platform.
2. Sometimes, we have ideas or opportunities that are too large, and we want to break them down into smaller ones while still addressing the big idea. Then, that big idea sometimes becomes epics that need a month or months to address, and the smaller ones become features that need weeks or days.

I'm looking forward to this feature as well, any update about this would be nice!


author: Sonya Petkunas
body: [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) do you have a ticket on your board that you are tracking the hierarchy feature that you could share?


author: Nick Beavers
body: [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312) This is a pretty important feature for us and is leaving a big hole in our workflow. We love Product Discovery but we are getting everything from small feature ideas to large project ideas in the funnel and many times the small features are sub-ideas of the larger project ideas. We cannot find a way to bridge the gap between the Discovery ideas to a traditional Jira Project becuase there is no intermediate staging environment to group many ideas into an Epic and then group related Epics into a Project/Release. In general, we are struggling to use these two things together effectively. Can you suggest any way to overcome this?


author: Sandra Juras
body: Hi! Just stumbled upon this and was wondering if this is going to ship anytime soon as the original question is already 2 years old? Any updates on this [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312)? Really looking forward to having this available!


author: Yassine
body: 2 years later still no grouping and no nesting (parent/child). That's unfortunate.   

That is probably the missing feature that will lead me back to airtable or just notion


author: Issam AGLAN
body: Hi Tanguy,

I might also be interested in having access to the project.

Thanks

Issam


author: Brent Johnson
body: Interested in this as well. Thanks for posting [@Baptiste Picard](/t5/user/viewprofilepage/user-id/4607851)


Tags: idea