We just got access to Premium and i am testing the ability to setup our opportunity solution tree in Jira Product Discovery. However i am pretty bummed that it seems you do not have the option of nested levels within a type, which was kind of the point for us. Our OST has like 3-4 levels of depth for the Opportunity type before we get to the solution level. How do you suggest i solve this? The beaty of an OST is that you can also move things around easily. If i have to create Opportunity level 1, level 2, level 3 etc it will quickly become overwhelming.
Hi @Delia Tomei Villadsen
Actually you can use the same time in multiple levels of a tree view.
You can do : Opportunity -> Opportunity -> Solution -> Solution -> Experiment
But what you can do is have variable levels, e.g. one idea has 2 opportunities above it, another only has one.
Aren't you able to select the same type twice when configuring a tree? If that's the case you might be hitting a bug. Let us know!
Hi Delia,
I think you’ve identified a real limitation of the current JPD hierarchy model.
In the Premium Tree view, you can configure up to 10 hierarchy levels, but each idea type can only be used on one level. So you can’t currently configure something like:
Opportunity → Opportunity → Opportunity → Solution
using the same Opportunity type at multiple levels.
Under the hood, JPD is still essentially a flat model where ideas are connected through Connection fields, and the hierarchy is a visualization of those relationships rather than a true recursive parent/child hierarchy.
For your OST, I’d probably avoid creating Opportunity Level 1, Opportunity Level 2, Opportunity Level 3, etc. unless those levels actually have different business meanings, because—as you mentioned—that can become difficult to maintain.
A more sustainable workaround could be to define meaningful types for the different layers, for example:
Strategic Opportunity → Opportunity → Problem → Solution
and connect them using Connection fields.
That preserves the tree structure without creating artificial numbered types.
If having the same Opportunity type recursively nested several levels deep is a core requirement, though, I don’t believe JPD supports that natively today, so that part would likely need to be treated as a feature request.
Hope this helps!
It looks like you're new here. Sign in or register to get started.
