Remove the GLQL dashboard panels in reading order flag

Brandon Labuschagnerequested to merge
631494-remove-glql-dashboard-panels-in-reading-order-flag into master

What does this MR do and why?

The glql_dashboard_panels_in_reading_order flag is a gitlab_com_derisk flag, so it can't be default-enabled. It has been enabled globally on GitLab.com production since 2026-10-02. To make it permanent, we remove the flag. This also turns the behaviour on for self-managed and Dedicated.

With the flag on (now always), every GLQL panel on an analytics dashboard view queues its query when it mounts. The shared dashboard request queue runs waiting requests by priority. The priority is the panel's index in reading order, so a view fills from the top down. A panel's comparison query and later pages keep the panel's priority. Background browser tabs now load fully.

The old path is deleted. Panels more than half a viewport below the fold used to wait until the user scrolled near them. Every request had priority 0, so they ran in arrival order.

  • Delete the glql_dashboard_panels_in_reading_order feature flag definition.
  • Remove the push_frontend_feature_flag calls from the Explore, group, and project analytics dashboards controllers, and the request spec examples that checked them.
  • In glql.vue, stop reading glFeatures. Remove the IntersectionObserver deferral. The resolver now always gets the panel's loadPriority as its priority.
  • Update the Jest spec. Drop the offscreen and observer tests and the flag on and off contexts. Keep one test that the load priority is passed to the resolver.

References

Screenshots or screen recordings

None needed. It only changes when and in what order GLQL panels query.

How to set up and validate locally

  1. Open /explore/analytics_dashboards/dap_impact.
  2. Pick a group.
  3. Open the browser network tab.
  4. Reload the page.
  5. Confirm GLQL requests fire for every panel on the view without scrolling.
  6. Confirm the panels fill from the top down.

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.

🤖 Generated with Claude Code

Merge request reports