👎
Roeland Schoppers
👍
Tatiana Chernogorova
👍
Ákos Botos
👍
Takayuki Hirota
👍
Andy McGrath
6
👎
Roeland Schoppers
👍
Tatiana Chernogorova
👍
Ákos Botos
👍
Takayuki Hirota
👍
Andy McGrath
6
Creating a roadmap with 2 levels
Tanguy Crusson・
827 views
5 comments
Roeland SchoppersFeb 6, 2024Basically you are saying your workaround is to create a dropdown for every 'epic' you created and then link every 'story' to that epic by having to go to that dropdow and selecting it. This seems like a non-solution to me.- Tanguy CrussonFeb 6, 2024Yeah I definitely wouldn't use that for Epic/story - that's way too granular. The smaller things we have in our discovery project are at the Epic level or above
José SantacolomaJuly 11, 2024(edited)I think using the parent-child model as in Jira Software used for the relationship Epic->User Story->Task delivers a smoother and better user experience for a X level roadmap for Boulder->Idea->Next level, etc. Then you just need to include "Parent" in the filter option.- AAnonymousNov 25, 2024(edited)Hi Tanguy, it seems you're using the Boulder field as a means to create parents for ideas, is that correct? Would you equate a Boulder to the same as an initiative of sorts, or is Boulder in this context rather a category? If Boulder is classified as an initiative, wouldn't it make more sense to have JPD support parent-child ideas instead? I'm sure you've discussed this already, curious to hear about it!
Andy McGrathApr 12, 2024Thank you Tanguy! 🙏 I recently came up with a similar solution to the hierarchy use case. Being able to publish now and share more widely in our organization, creating a "Boulder" field added the extra context people needed to see the big picture I had in my head.
Takayuki HirotaAug 1, 2024Thank you Tanguy! 🙏 In my understanding, your approach looks like a cascading select field type. If JPD supports cascading select fields, it will allow creators to handle 2 levels roadmap easily, I think. Of course, it will be challenging.
