Current State:

Parent-to-Child: Child field does dynamically filter based on Parent selection

Child-to-Parent: No auto-population of Parent field when a Child value is selected

This leads to data inconsistency and poor user experience

Currently, there is no bidirectional dynamic behavior between parent and child Asset object fields, leading to manual selection overhead and potential data inconsistency.Selecting a Child value does not auto-populate the corresponding Parent value
 

Proposed Future State:

When using cascading Asset object custom fields with a Parent-Child relationship and Filter Issue Scope, the fields should dynamically update in both directions:

When a Parent field value is selected, the Child field should dynamically filter to show only relevant child objects.

When a Child field value is selected, the Parent field should automatically populate with the corresponding parent object.
Selecting a Parent value should immediately and dynamically filter the Child field to show only relevant child objects .

Selecting a Child value should automatically set/suggest the corresponding Parent value