Idea linked in delivery tab via implements doesnt show child issues/linked delivery work items

[binh_pham]

Hi,

we have a lot of cross team dependencies.  

1. If you link to Idea X delivery work items from several teams (Jira projects) they will be correctly counted into idea X progress and can be seen including child work items but
2. If you link to Idea X another Idea Y that has its own epics via implements relationship, Idea Y will be seen in delivery tab of Idea X but you cant see Epics of Idea Y and they dont count to Idea X progress. see screenshot

Is this intentional? It causes some complications e.g. Product manager X needs to know all dependent Jira delivery work items (not just from his dev team) and sometimes new are created over time.

If JPD would support use case #2, Product manager X would just need to know besides his Epic(s) only dependent Ideas.

Thx

B.

[Bill Sheboy]

Hi @binh_pham 

I hypothesize what you are observing is likely the intended behavior because...

• Jira Product Discovery (JPD) has Ideas, such as representing the portfolio of things to implement
• For each Idea, zero-to-many "Delivery Tickets" may be associated, using the linking type specific to JPD
• And those delivery tickets show their child issues based on the parent / child linking of issues (which is different from JPD delivery ticket link types)
• Thus the "Delivery progress" is based on those issues (the parents and children)

The feature does not "recursively" detect other customer intentions to use an Idea to implement another Idea as those are not parent / child relationships.  (In my opinion, the JPD UX could make that more clear to customers by not allowing adding other issue types to "Delivery tickets" and not allowing the use of the "Implements" link type for things other than Ideas.)

If you believe this would be a useful feature, consider using the "Give feedback about Jira" under the question mark at the top-right of the page view.

Kind regards,
Bill

[binh_pham]

Hi, yes thx for the reply.

It would be useful at least in our case as we have platform and complicated subsystem/R&D teams that have their own JPD projects and roadmaps with ideas that usually support ideas of product teams. 

That an Idea could be linked as a delivery work item to another idea seems quite useful. Maybe the premium feature Idea hierarchies is addressing this although its not exactly hierarchy in our case but more like a chain of ideas (R&D ->platform->product team)

[Kathrine Lønning]

We have the exact same issue in our organization and is now considering to merge together the JPD projects just to get everything planned in one place, ordering delivery tickets from multiple dev teams, but still kepp track on Idea level. 
BUT - also waiting for hiearchy functionality to see if this will help out on this issue.. 

Let me know if you figure out a good and efficient way of tracking this in your end. :) 

[Tanguy Crusson]

Hi, I think this may be something you can solve with this upcoming feature (part of the premium plan)

[binh_pham]

edit: Attached screenshot