JPD types in issue type hierarchy for Jira Plans

[Thorsten Kamann]

Hello,

I am playing around with the new beta feature types hierarchy in JPD. We have here this issue type hierarchy:

Initiatives → Customer Journey/Epics → Stories

With the new beta feature, I think about to move the type Initiative to JPD as type, so I can build the first part of the hierarchy in JPD:

Initiative → Customer Journey

But Jira Plans doesn't recognize the types from JPD. In JQL there isn't such a problem. There I can query

type = Idea (or in my case Initiative)

Is this a known behavior or is it planned to implement?

Best Thorsten

[Tanguy Crusson · Accepted solution]

Hi, yes, it's on the roadmap and not supported today. 

what you can do on Plans is group all epics by Customer Journey (the level you connect to epics)

[Thorsten Kamann]

Hi @Tanguy Crusson ,

I think, I am some steps further. 

I follow your looms about idea hierarchies (what is very well) I have such a structure:

Goals

→* Business Initiatives

   →* Themes

      → * Experiments

      →* Customer Journey → Epic

                                                 →* User Story

   →* Enabler

You see, the only level without an 1-n relation is Customer Journey and Epic. This is mapped one to one. This is done because of different scopes of each issue type. The Customer Journey is user-centric and lives in JPD and Confluence, and the Epic is the main delivery item living in Jira. 

In Plans, the problem to make Customer Journeys part of the issue type hierarchies is gone. Instead, I use the idea field in plans.

But the problem isn't gone, only moved a level up. Themes are an idea type, too. If I want to see all level of issue types, I need themes in plans. But for now this is more part of the program view in plans not the operational plan.

Can you say when you plan to deliver this feature? Is it more later this year or next year?

Thanks.

[Tanguy Crusson]

Thanks for the feedback @Thorsten Kamann - I don't have dates to share yet.