You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Free organizations can connect Slack, but no Slack notifications are ever sent #2702
A project in a Free plan organization can connect Slack, and the app reports success. Notifications are never queued for organizations without premium features, so the Slack channel never receives anything, and nothing in the UI says why. If the user changes the Slack notification switches afterwards, they get a generic error instead of the upgrade dialog.
In an organization on the Free plan, open a project's Integrations page and click Connect Slack.
Complete the Slack authorization. The app shows "Successfully connected Slack integration" and default Slack settings are saved.
Send a new error to the project. Nothing arrives in Slack.
Toggle any Slack notification setting. The app shows "Error updating Slack notification settings. Please try again." because the 426 isn't handled.
Expected
Connecting Slack on the Free plan returns the plan-limit error (426) before the OAuth token is stored, and the page shows the upgrade dialog, as it already does for webhooks. Settings changes also show the upgrade dialog instead of a generic error.
Suggested fix
In AddProjectSlack, load the organization and return the same PlanLimit validation result used in SetProjectIntegrationNotificationSettings when !organization.HasPremiumFeatures. Ideally check this before exchanging the code, or revoke the token afterwards.
In updateSlackNotificationSettings, call showBillingDialogOnUpgradeProblem.
Optionally show a notice on the Slack section for organizations already connected on the Free plan.
Activity
Fix regression check, token Location, and small app bugs (#2716)