Skip to content

fix(jira): Halt status sync when the target status has no transition - #131738

Draft
sentry-junior[bot] wants to merge 1 commit into
masterfrom
rr/fix-jira-status-sync-silent-failure
Draft

sentry-junior[bot] wants to merge 1 commit into
masterfrom
rr/fix-jira-status-sync-silent-failure

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

When outbound status sync can't find a Jira workflow transition to the configured status, sync_status_outbound logged jira.status-sync-fail and returned. The task then recorded the OUTBOUND_STATUS_SYNC lifecycle as a success and fired IntegrationIssueStatusSyncedEvent, so these failures were invisible in our metrics.

This raises IntegrationConfigurationError from Jira Cloud and Jira Server in that case. The task now treats it as a halt, the same way sync_assignee_outbound does: no retries (it's a config issue, so retrying won't help) and no synced analytics event. Also removes the 2018 TODO(jess).

No other sync_status_outbound implementation raises IntegrationConfigurationError today, so the new halt only affects Jira.

via richard.

--

View Session [Sentry]

Outbound status sync logged jira.status-sync-fail and returned when no
workflow transition reached the configured status, so the task recorded
the lifecycle as a success and fired the synced analytics event. Raise
IntegrationConfigurationError instead and halt on it in the task.

Co-Authored-By: Richard Roggenkemper <richard.roggenkemper@sentry.io>
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Nov 19, 2026

This branch has not been deployed

No deployments
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.

0 participants