If I understood the connections concept I should be able to visualize the connections in any direction. There is no real parent or child relationship. When I try this with a simple board view it does not seem to work: * Types: Initiative, Phase * Connection fields: Initiatives, Phases * Created one initiative with 3 phases * Roadmap board with Now Next Later. * Initiative board: filter by type Initiative, filter by Phases "group by column" -> works * Phase board: filter by type Phase, filter by Initiatives "group by column" -> doesn't work In the Initiative board I see the Phases as sub items on the card. I would expect to see the same structure reversed in the Phase board. I've tried reducing the simplicity down to nearly zero, but can't make it work. Is my assumption correct, this should work? Or did I misunderstand the feature.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Viewing connection hierarchies in both directions

Freyr Gudmundson

If I understood the connections concept I should be able to visualize the connections in any direction. There is no real parent or child relationship.

When I try this with a simple board view it does not seem to work:

Types: Initiative, Phase
Connection fields: Initiatives, Phases
Created one initiative with 3 phases
Roadmap board with Now Next Later.
Initiative board: filter by type Initiative, filter by Phases "group by column" -> works
Phase board: filter by type Phase, filter by Initiatives "group by column" -> doesn't work

In the Initiative board I see the Phases as sub items on the card. I would expect to see the same structure reversed in the Phase board. I've tried reducing the simplicity down to nearly zero, but can't make it work.

Is my assumption correct, this should work? Or did I misunderstand the feature.

Accepted answers

Tanguy Crusson

Hi! I read your question a few times and still not sure I get it.

Here's me trying stuff along those lines, let me know what's what and I can try to create a set up for you to reproduce!

https://www.loom.com/share/2accc4a3205e43a288e8b7f3db399d96?sid=78d39922-db84-496a-9321-4634831124fb

All comments

Tanguy Crusson

Hi! I read your question a few times and still not sure I get it.

Here's me trying stuff along those lines, let me know what's what and I can try to create a set up for you to reproduce!

https://www.loom.com/share/2accc4a3205e43a288e8b7f3db399d96?sid=78d39922-db84-496a-9321-4634831124fb

Freyr Gudmundson

Hi! Thank you so much for the video response, super helpful (was on vacation, ergo the belated response).

I will go through this and see if I can figure out what I am doing wrong. Honestly, I am also not entirely sure what I was trying to accomplish, am just learning what JPD can do and trying stuff out. But what you showed me is spot on, that's what I expected to see on my side but didn't. So thanks! I can debug it now

Freyr Gudmundson

For clarity, here's what I was trying to do:

Screenshot 2025-07-22 100436.png

Essentially just flip around the view. On the top I'm viewing the roadmap from a "Top Priorities" perspective, and on the bottom from a "Phases" perspective.

What I was missing was simply filtering for the right "connection" field. It was a really simple error to make on my part, but was surprisingly tricky to find. I hadn't yet internalized that in order for the connected item to be visible, it's the connection field that matters. It has to be marked as a visible field in the Fields area, it's not enough to add the type to the filter.
It was essentially a fix to my understanding of the way the connection feature is created. Just wanted to share here in case others benefit