Skip to content

fix(github): Ungate inbound issue status sync from removed feature flag#119079

Open
souredoutlook wants to merge 1 commit into
masterfrom
fix/github-inbound-status-sync-feature-flag
Open

fix(github): Ungate inbound issue status sync from removed feature flag#119079
souredoutlook wants to merge 1 commit into
masterfrom
fix/github-inbound-status-sync-feature-flag

Conversation

@souredoutlook

@souredoutlook souredoutlook commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Closing or reopening a GitHub issue stopped resolving/unresolving its linked Sentry issue (GitHub → Sentry inbound status sync). Outbound sync (Sentry → GitHub) was unaffected, matching the customer reports.

GitHubIssueSyncSpec.get_resolve_sync_action gated on check_feature_flag(), which checked organizations:integrations-github-project-management. That flag was removed from the registry in #116551 — deemed "zero usage" because the only reference builds the flag name dynamically from self.model.provider, so a literal grep missed it. features.has() on an unregistered flag raises FeatureNotRegistered internally and returns False, so get_resolve_sync_action always returned NOOP and the inbound sync silently no-oped.

The flag had previously been registered in #114789 and the check was moved into the shared spec in #103422.

Fix

Both github and github_enterprise project-management flags are fully rolled out (GA at 100% in sentry-options-automator), so this drops the gate entirely rather than re-registering a flag no one maintains. This restores inbound status sync for both GitHub and GitHub Enterprise (GHE inherits GitHubIssueSyncSpec).

Fixes GH-110299

Closing or reopening a GitHub issue stopped resolving/unresolving its
linked Sentry issue. GitHubIssueSyncSpec.get_resolve_sync_action gated on
check_feature_flag(), which checked organizations:integrations-github-project-management.

That flag was removed from the registry in #116551 (deemed "zero usage"
because the only reference is built dynamically from self.model.provider,
so a literal grep missed it). features.has() on an unregistered flag raises
FeatureNotRegistered internally and returns False, so get_resolve_sync_action
always returned NOOP and the inbound sync silently no-oped. It had previously
been registered in #114789 and moved into the spec in #103422.

Both github and github_enterprise project-management flags are fully rolled
out (GA at 100%), so drop the gate entirely rather than re-register a flag no
one maintains, restoring inbound status sync for GitHub and GitHub Enterprise.

Fixes GH-110299
Co-Authored-By: Claude <noreply@anthropic.com>
@souredoutlook souredoutlook requested review from a team as code owners July 6, 2026 20:22
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Jul 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Closing a GitHub issue does not update linked Sentry issues

1 participant