ref(inbox): use new issue-inbox flag on backend - #122421
Conversation
| manager.add("organizations:issue-summary-experimental", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, api_expose=False) | ||
| # Enable new issue stream progress views | ||
| manager.add("organizations:issue-stream-progress-ui", OrganizationFeature, FeatureHandlerStrategy.FLAGPOLE, api_expose=True) | ||
| # Show the "recommended" sort as an option in the issue stream sort dropdown |
There was a problem hiding this comment.
Bug: Removing the issue-stream-progress-ui feature flag will cause the inbox page to render a NotFound error because the frontend still relies on this flag to render.
Severity: CRITICAL
Suggested Fix
This change has a deployment dependency on a frontend pull request. Ensure the frontend PR, which removes the dependency on the issue-stream-progress-ui flag, is merged and deployed before this backend change. Alternatively, coordinate the deployment of both PRs to happen simultaneously to avoid breaking the inbox page.
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#L382
Potential issue: The pull request removes the backend registration for the
`organizations:issue-stream-progress-ui` feature flag. However, the frontend code in
`static/app/views/issueList/pages/inbox.tsx` checks for the presence of this flag to
render the inbox page. If this backend change is deployed before the corresponding
frontend change that removes this check, the condition
`organization.features.includes('issue-stream-progress-ui')` will always be false. This
will cause the component to return a `NotFound` page, making the entire inbox feature
inaccessible to all users.
Also affects:
static/app/views/issueList/pages/inbox.tsx:151
Did we get this right? 👍 / 👎 to inform future reviews.
There was a problem hiding this comment.
This is expected, the other PR changes the frontend pieces
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit d3e3743. Configure here.

#122110 must be merged and deployed first
Drops
issue-stream-progress-uifor the newissue-inboxflag