feat(queue): Register insights-queue-dashboard-migration feature flag#109332
Merged
DominikB2014 merged 2 commits intomasterfrom Feb 26, 2026
Conversation
Add the queue module feature flag to the temporary features registry, following the same pattern as the existing web vitals, frontend overview, and frontend assets dashboard migration flags. Co-Authored-By: Claude <noreply@anthropic.com>
github-actions
bot
added
the
Scope: Backend
edwardgou-sentry
approved these changes
Feb 25, 2026
…re-flag-for-queue-module-to-dashboards
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Comment on lines
+241
to
+242
| # Enable queue dashboard on dashboards platform | ||
| manager.add("organizations:insights-queue-dashboard-migration", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, api_expose=True) |
Contributor
There was a problem hiding this comment.
Bug: The new feature flag organizations:insights-queue-dashboard-migration is registered on the backend but is not used in the frontend, rendering the flag and its associated feature non-functional.
Severity: MEDIUM
Suggested Fix
Implement a frontend utility hook, similar to useHasDashboardsPlatformizedHttp(), to check the state of the organizations:insights-queue-dashboard-migration feature flag. Use this hook within the queue module's landing page to conditionally render the new platformized dashboard view when the flag is enabled.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.
Location: src/sentry/features/temporary.py#L241-L242
Potential issue: The new feature flag `organizations:insights-queue-dashboard-migration`
is registered in the backend but is never checked in the frontend code. Other similar
feature flags for different modules, like `insights-http-dashboard-migration`, have
corresponding frontend utility hooks (e.g., `useHasDashboardsPlatformizedHttp()`) that
are used to conditionally render a "platformized" dashboard. The queue module lacks any
such hook or logic in its landing page, `queuesLandingPage.tsx`. As a result, the flag
is non-functional, and enabling it for an organization will have no effect, preventing
the rollout of the new platformized queue dashboard experience.
Did we get this right? 👍 / 👎 to inform future reviews.
Contributor
Author
There was a problem hiding this comment.
You have to register a flag before using it, many times devs will create the flag before starting development
DominikB2014
deleted the
dominikbuszowiecki/browse-365-create-feature-flag-for-queue-module-to-dashboards
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Register the
insights-queue-dashboard-migrationfeature flag in the temporary features registry.This follows the same pattern as the existing insight module migration flags (web vitals, frontend overview, frontend assets) and will be used to gate the queue module's platformized prebuilt dashboard experience behind a Flagpole-controlled rollout.