Type Hierarchies vs. Grouping / Filtering vs. "Grandparents"

[Jonathan Prisant]

I am absolutely loving the flexibility of hierarchies in JPD Premium! What's funny is I initially create a global field called "Idea Type" that essentially tried to facilitate this sort of approach. Flat & scattered items → flexible hierarchy visualization provides so much opportunity!

I have watched the videos and am struggling to visualize the items as desired for our directors & executives

Context

Types: Theme, Initiative, Feature

Conceptual Hierarchy [for FY Delivery Plan]: 

• Themes
  • Initiatives
    • Features

My Goal

Using a Board view, I am trying to show:

• Columns = Initiatives
• Type items in the board = Features, grouped by Quarter

... but, I only want to show all of the Initiatives [as columns] for a specific Theme.

Since Features...

• Have an Initiative, which have a Theme
• Do not have a [conceptual "grandparent] Theme

Sample Work Items

Theme: Melange Mastery

Initiatives: (all with Theme "Melange Master"), with ["children"] Features:

• [Initiative] Spice Flow Optimization
  • [Feature] Arrakis Dust Vacuum
  • [Feature] Muad’Dib Prophet Query Language
• [Initiative] Shielded Delivery Pipelines
  • [Feature] Harkonnen Intrusion Alerts
  • [Feature] Mentat Merge Validator

For example, I want a Board, with:

• Columns [only with Initiatives for Theme "Melange Mastery"]:
• With Feature cards in each column [grouped by Quarter]

Column #1: Spice Flow Optimization. with cards for Features:

• Arrakis Dust Vacuum
• Muad’Dib Prophet Query Language

Column #2: Shielded Delivery Pipelines. with cards for Features:

• Harkonnen Intrusion Alerts
• Mentat Merge Validator

My Question

❓How do I accomplish my desired outcome?

... It seems there is a similar question for List Views.

[Tanguy Crusson · Accepted solution]

Hi Jonathan, you're right: in the current shape of the feature the "sub-child" doesn't know anything about the "parent". We're currently discussing ways to enable things like this.

In the meantime what some teams are doing is using automation rules to copy over connections, so the "sub-child" gets connected to the "parent" when the "child" is connected to that "parent". 

https://www.loom.com/share/5e38d79d0b614fb6a7eb7b9c3146e5ba?sid=a0e5d940-507c-44be-bd92-4bfd09e6de6c

[Jonathan Prisant]

Thanks for the response. What's exciting is with how y'all have architected the solution... there's so much opportunity and flexibility!

I'll check out that video.