Why do fields get greyed out in advanced roadmaps when filtering?

[Jade Melcher]

Does anyone know why issues are greyed out in advanced roadmaps when filtering issue details? our leadership team has concerns with this and it has caused confusion with stakeholders.

Without filter:

With filter:

[Nic Brough -Adaptavist- · Accepted solution]

It looks to me like they're greyed out to stop you trying to click on them when they might not be valid for the filters you are about to start defining on the right-hand side.

[Jade Melcher]

Yes, I think in other words if the fields don't match the filter exactly, but are children, they will be displayed but greyed out. A workaround would be to include a key of some sort in all children. 

[Robert Synofzik]

Good point and exactly the answer I needed. Thanks!

[Bev Feierbacher]

@Nic Brough -Adaptavist- I tried the workaround using labeling and still seeing the greyed out "children" that match none of my filters for the ones I truly want to show. 

Any other suggestions than using labeling? Note: this is not a source issue, I just don't want to see the children (even in a greyed out format) if they do not match the filters (including the label I used) for the specific "view".