Problem:
Dynamic Filtering does not currently work when creating new items directly on a board or via the + New button, even when the fields used for filtering are known or set during creation. This creates an inconsistent and frustrating experience for users.
Scenario 1 – Required Field with Dynamic Filtering on Board View:
- On a board, I have a required field.
- This field has Dynamic Filtering applied.
- The field used in the Dynamic Filtering is also referenced to set the rows or columns of the current view.
Scenario 2 – Creating a New Entity:
- On the same board, I click the + New button, which opens a form with several fields.
- One of the visible fields has Dynamic Filtering, and another visible field is used in the filtering logic.
- When creating a new entity directly on the board or via the + New button, the Dynamic Filtering does not work.
The system shows a message like: “Filters aren’t applied because they have missing ‘𝑥’ dynamic values”. Essentially, because the entity does not yet exist, the filter cannot reference its values.
Expected Behavior:
The filter values should be inferred during creation:
- For a board-created item, the referenced field should default to the board context where “New…” was clicked.
- For a + New form, the referenced field should use the value the user has just selected or entered.
This would make the creation experience consistent with how Dynamic Filtering works for existing entities.
Why This Matters:
Dynamic Filtering is most useful during the creation process, as users are defining the critical values at that point.
Currently, users see inconsistent options or must make selections after creation, which is inefficient and confusing.
Aligning this behavior would improve usability and reduce friction for workflows that rely heavily on dynamic field relationships.
