How to create a single, holistic view of goals, ideas, & delivery tickets in JPD?

[David Nadri]

We are trying to create a single, holistic/hierarchical view in Jira Product Discovery (JPD) of all our active ideas with their delivery tickets (epics, stories, etc) nested underneath them. However, the delivery tickets are only visible from the Delivery tab within each idea (not across all ideas in the view):

We need a single view in JPD (or Jira Software) that shows the complete picture of our product development process - from goals > ideas > epics > stories > to sub-tasks - without constantly needing to switch back and forth between JPD and Jira Software. Here's a concept mockup:

I've explored various options within JPD and Jira Software, but haven't found a way to achieve this. While I understand the different purposes of JPD (discovery) and Jira Software (delivery) [see the JPD guide], there's still a legitimate need for a single, holistic view that shows how everything fits together & ladders up to the 'why'. 

For example, while other tools may serve specific aspects of our workflow (e.g., Confluence/Atlas for strategic context/goals, JPD for ideas, Jira Software for delivery tracking), there's no single integrated view available.

In our workflow, as ideas transition from "In Discovery" to "In Delivery," we require visibility of all associated delivery tickets within JPD. This ensures all stakeholders can quickly & easily grasp the project's scope and alignment with objectives, monitor progress across the idea/epics/stories/etc in one place, and see other properties of the delivery tickets for full transparency.

 Any guidance on achieving this or alternative approaches would be much appreciated.

Thank you for your help!

[Margo Sakova - OKR Board for Jira by Oboard]

Hi again, @David Nadri 🙂

I believe Advanced Roadmaps with a custom hierarchy and custom issue types for goals, key results, and ideas could be a suitable solution. Here is my draft:



I've detailed this approach in my Jira OKR guide. Regarding JPD, the method you've described—checking the delivery tickets per each idea — is the only approach I've found as well.

It seems to me that JPD is more focused on exploration rather than the actual delivery phase, even though they have the link.

[David Nadri]

Hi @Margo Sakova - OKR Board for Jira by Oboard - thanks for your input.

We've explored Jira Premium and it's not a fit for us at the moment, so I'm looking for a native way to do this (see mockup below) with the Jira Standard plan and/or JPD.

I understand that JPD is more focused on discovery/exploration & Jira is more focused on delivery, but there's still a very valid need to see the full picture in one place - from OKR/goals to ideas to delivery tickets.

[Margo Sakova - OKR Board for Jira by Oboard]

Hi @David Nadri

I've double-checked, and haven't found any ways to achieve the setup you're looking for. If the number of goals is not huge, you may try to use the Atlassian OKR template in combination with Jira issues macros.

I hope that helps.

[Amina Bouabdallah]

Hi there, 

We are currently exploring a path so that everything laddering up to the why becomes possible natively. There exists solutions right now to see multiple subtrees of your entire tree separately.   

If you are keen to speak with us for our testing, please book time with us: https://calendly.com/aminabh/jpd-hierarchies-discovery-call?month=2024-02 

Cheers,

Amina

[David Nadri]

@Amina Bouabdallah - will do, thank you for making time to discuss this with me. I appreciate it!

[Michelle]

Hi Amina,

If possible, please share the outcome of the discussion.

I've just implemented JPD in my organization, and having an OKR view is also a challenge for us.

Thank you!

Cheers,

Michelle

[David Nadri]

Hi @Amina Bouabdallah - any updates you could please share on this?

[Gergely Fehér]

Hi,

I can imagine 2 ways to have a view like this:

- With Structure app you can create custom trees of issues based on their links and hierarchy.

- With Advanced Roadmaps - add a few automations, to fill a "Parent Idea" field with the key/summary of an idea in all related issues, then in a plan view, group the issues by this fields value.