Are there plans to enable a parent-child relationship for ideas?

[Anna Keeton]

We use the opportunity solution tree in our product teams, and so parent-child relationships are really key to visualizing ideas.

Currently I've hacked this by creating new fields and then relying on tagging. We have a field for type (opportunity/solution), and then a field for opportunity (opportunity names), and then a field for parent opportunity (parent opportunity names)....

But as you can imagine, it's not very scalable, and anytime we find a new opportunity, it's quite a bit of faff

Does Jira plan to bring this functionality to JPD in the near future?

[Andrew]

Hi. 

Same thing for me. we would parent/child relationship for a few different ways of planning. 

We summarize features into larger initiatives and roll up initiatives into programs. 

At the program level, i think the drop-down field solution would be an OK workaround because there programs are small in number (like 3-4 strategic themes for the year). 

But when it comes to features and initiatives, as our list of initiatives grows i think the parent child relationship will be needed. 

[Amina Bouabdallah]

hi there ! yes, I am doing discovery on the matter now! Any chance you might chat on the phone ? Here is the link to book time: https://calendly.com/aminabh/jpd-hierarchies-discovery-call

Looking forward to our chat!

Amina

[Andrew]

Happy to chat if you like!

[Amina Bouabdallah]

Hello Folks! this is currently in discovery in the JPD PM team! :) 

[Marek Cais]

Great news. I'm looking forward to it.

[Tom Kent]

@Tanguy Crusson shared this loom video about a concept they're working on for this problem, but I don't know if it will make it into the final product.

It is less of a hierarchy, and more of a built-in support for the type of label relationships you are already using.

Separately, there is also a feature being worked on for Advanced Roadmaps on the regular Jira software side which would allow grouping issues by ideas. That's kind of like a parent-child relationship, insofar as you can select a JPD idea as the parent for Jira tickets.

[Marek Cais]

Same here. I'm considering a simplified version of what you're doing: ideas are ideas (closer to solutions) and opportunities are a custom field (tag) and the view is set to group by "opportunities". That gives you an almost tree like view. Unfortunately you need to edit the field to add more opportunities and it does not allow for sub-opportunities. Plus no way to add context to opportunities, since they're just a field.