📣 Feature update: Hierarchies in Jira Product Discovery

[Maggie Cameron]

We aren't on the Premium Plan, but I'm still seeing the "connections" feature. Has this been extended to all plans?

[Tanguy Crusson]

@Maggie Cameron that looks like a bug! We're fixing it now, thank you

[Kevin Sniokaitis]

It looks like there has been some updates on this functionality but the documentation / how-to is still showing the previous way to setup. Any chance there's a new video on how to setup with the changes?

[Caleb Amesbury]

We have upgraded to premium to try out and build out our OST.  When will the Tree view become available?

[Tim Cromwell]

Hi @Tanguy Crusson / JPD Crew, same as @Caleb Amesbury I'm eager to find out when the Tree View might become available too... Any news you might be able to share?  Thanks! 😀

[Mykenna Cepek]

(wrong acct, see next comment)

[Mykenna Cepek]

It seems misleading to write "you can create hierarchies" and also write "It’s still a flat model, where all ideas are at the same level".

The more accurate statement was "you can use views to visualize them in a hierarchy", but that was pretty buried and subtle.

The title of this article is "Hierarchies in Jira Product Discovery". Something like "Hierarchical Views in Jira Product Discovery" would be clearer.

Much of Atlassian's user base is very familiar with the work item type hierarchy, which includes parent/child relationships. This is definitely not that. Clarity will help reduce confusion, frustration, and disappointment.

[Maurizio Mancini]

@Tanguy Crusson - While this feature is interesting, when are you planning on doing the essential feature of connecting JPD to really work with Jira Plans beyond the basic functionality that we have today of being able to show an idea in a Jira Plan?

I know you said it is on the Roadmap but it has been on the roadmap for a long time and it is the one feature that would really make JPD more useful to large companies who have numerous teams delivering work that is connected to the Ideas in JPD.

Thank you!

[Jena Miller]

Hi JPD Team --

Thank you for all your hard work on these features!  We are using them and loving them! 

I wanted to check in on any approximate timelines for list view functionalities.  We have many important use cases throughout our roadmap planning process that require us to be able to see three levels of ideas; however, a board view is not sufficient.  We need to be able to provide a view to a specific team (development team, for example) to fill in their metadata fields for each idea - something that's not easy to do via a card on a board but is very easy to do in a line item in a list.  

Happy to detail additional use cases but primarily looking for a timeline estimate on the 3 levels of ideas on a list view, if possible. 

Thank you so much!

Jena 

cc: @Regina Whyte @Sharon Connell 

[Mirko Grahnert]

Hey @Tanguy Crusson. Curious to hear if there are any updates on the OST view? This is probably the biggest limitation of JPD for us at the moment, because it means that teams have to rely on separate tools for their OSTs (Miro) and product backlog and roadmaps (JPD). I can see that the Tree View is still in the 'Up Next' column on your roadmap. Any rough idea how far we are away from a first Beta?

[Tanguy Crusson]

Hi Mirko, unfortunately this one is still "next" in our roadmap - we haven't started on it yet, the rest of the feature took much longer than expected to get right. We're going to get to it though!

[Ian Muirhead]

With the goal to produce the hierarchy you're going to need to introduce non-flat hierarchy - (I think???). How do you foresee that impacting the implementation here.

I would also love to be able to bulk copy idea links via CSV to be able to import into a whiteboard tool (figjam) for laddering/affinity mapping.