Issue Summary

In the NEW Feature Grid, filtering by a specific "Jira Space" fails to return features that are associated with multiple Jira Spaces. While the Legacy Feature Grid correctly identifies and displays these features, the NEW grid appears to only check the primary table where the Jira Space Key is null for multi-value entries, failing to query the secondary table where these associations are stored.

Steps to Reproduce

1. Create a Feature and assign it to multiple Jira Spaces (e.g., "Space A, Space B, Space C").

1. Ensure the feature has stories assigned to a team belonging to one of those spaces (e.g., "Space C").

1. Navigate to the NEW Feature Grid.

1. Apply a filter: Jira Space = Space C.

1. Observe that the feature is missing from the results.

1. Navigate to the Legacy Feature Grid and apply the same filter; observe that the feature is correctly displayed.

Expected Results

The NEW Feature Grid should return all features associated with the filtered Jira Space, regardless of whether the feature is linked to one or multiple spaces.

Actual Results

Features with multiple Jira Spaces are excluded from the NEW Feature Grid results when filtering by a single Jira Space name.

Workaround

Users can continue to use the Legacy Feature Grid to view a complete list of features when filtering by Jira Space. Alternatively, ensuring a feature is only linked to a single Jira Space will allow it to appear in the NEW grid, though this may not align with organizational data requirements.