Are issue types and hierarchy coming to JPD?
Asked by James Conway:

It would be really useful to be able to define different types of issue within JPD, e.g. to implement Opportunity Solution Trees or treat ideas (of solutions) differently from needs or problems.  

Along those lines, the ability to define issue type hierarchy and select field hierarchy would help organisation.

Is this something on the roadmap?


Answers:
author: Tanguy Crusson
body: Hi [@James Conway](/t5/user/viewprofilepage/user-id/5356179) , what [@Nick H](/t5/user/viewprofilepage/user-id/2540930) said, but also: yes, it's on the roadmap. In fact we landed on a solution that's looking promising and the team met to kick this off, starting with a technical spike. We'll post in this community when we have something in early access (but we're still a while away from being able to do that).

comments: author: James Conway
body: Thanks [@Tanguy Crusson](/t5/user/viewprofilepage/user-id/502312)! If my org can be part of the early access that would be really cool, I know its an adoption pain for many PM Team members.


author: Nick H
body: Hi [@James Conway](/t5/user/viewprofilepage/user-id/5356179) ,

It's not currently possible to create different JPD issues types besides Ideas, but it's something engineering is considering as mentioned in this page, along with a workaround:

[Frequently asked questions](https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Frequently-asked-questions-about-the-product-how-do-I/ba-p/2002378) - about the product (how do I...?)
>
> #### Can we create different issue types and their relationships? (e.g. parent/child or opportunity/solution) {#toc-hId-348675272}
>
> Not yet, but it's on the roadmap. In the meantime you can use the flexible fields and views system to do this. Here is an example:
>
> [Demo: grouping solutions by opportunities](https://www.loom.com/share/c5acafb1584740c98f6871667bac6df8). And here's a [recording of how to reproduce this configuration](https://www.loom.com/share/c74c8cc8e5be4daaa4498bb8d3397bcd)

comments: author: William Perkins
body: I have used this workaround to quite good effect to create a hierarchy of Goal - Initiative - Feature.

I would still dearly love a formal structure, but the work around does what it says on the tin.

<br />

The thing that it lacks is a very easy way to see associated child issues. I would love to open a goal ticket and see all the nested initiatives. Maybe there is a known work around for this?


author: William Perkins
body: Thanks for the explanatory video by the way, really helpful when setting up my hierarchy.


author: Tanguy Crusson
body: Cool, thanks for the feedback [@William Perkins](/t5/user/viewprofilepage/user-id/1537485) . You can associate ideas together by linking them (then the link is visible on both ideas).

We're currently working on a solution that makes all of this easier and more native.


author: William Perkins
body: That works, thanks!


author: Gary Spross
body: I'd love to see JPD get the ability to be created as Company-managed projects. This would solve for this issue, as well as the problem we are seeing in our instance with a ridiculous number of duplicated fields. Many of these fields come OOTB when you create a JPD project, so regardless of having a process in place for generating Global fields or unique field names, it doesn't matter. It also doesn't help that project admins can create fields within the project themselves, so getting everyone to follow a process for this aspect is even more difficult.