Security dashboard: add separate feature flag for tracked ref filters
What does this MR do and why?
Adds a dedicated WIP feature flag, security_dashboard_tracked_ref_filter, to control the visibility of the tracked reference filter on the Security Dashboard.
This decouples the filter's visibility from the broader vulnerabilities_across_contexts feature flag, allowing for more granular rollout control while the BE is still being developed.
It also updates the data passed to the component, replacing the trackedRefs array with a more structured defaultBranchContext object, which follows a performance optimisation that was introduced a while back (already on the Vulnerability Report).
Finally, it also includes passing the filter arguments (the trackedRefIds) through to the GraphQL queries.
References
Screenshots or screen recordings
| before | after |
|---|---|
 |
 |
How to set up and validate locally
- Enable the feature flag by navigating to: http://gdk.test:3000/rails/features/security_dashboard_tracked_ref_filter
- Ensure the vulnerabilities_across_contexts feature flag is also enabled: http://gdk.test:3000/rails/features/vulnerabilities_across_contexts
- Visit a project's Security Dashboard.
- Verify that the tracked reference filter is visible in the filter bar.
- (Optional) Disable the flag via the same URL and verify that the filter is no longer visible.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.