Skip to content

Deprecation issue: Slack Notifications integration

For guidance on the overall deprecations, removals and breaking changes workflow, please visit Breaking changes, deprecations, and removing features

Deprecation Summary

As we're consolidating all Slack capabilities into the GitLab for Slack app, we've deprecated the Slack notifications integration. Users can now use the GitLab for Slack app to manage notifications to their Slack workspace.

The GitLab for Slack app does not have full feature parity with the deprecated Slack notifications integration (at time of writing, as of 16.8). Those features will block the removal of the Slack Notifications integration until they are completed. These blocking features are listed in Removal of Slack Notifications Integration (&8673).

Progress on the removal can be followed in &8673.

Breaking Change

The removal of the integration will be a breaking change. Customers should move to the GitLab for Slack app.

Affected Topology

All users of the Slack Notifications integration.

Affected Tier

All tiers.

Checklists

Labels

  • This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
  • This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

Please add links to the relevant merge requests.

  • As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
  • On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post.
  • On the major milestone:

Mentions

  • Your stage's stable counterparts have been @mentioned on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.
    • To see who the stable counterparts are for a product team visit product categories
      • If there is no stable counterpart listed for Sales/CS please mention @timtams
      • If there is no stable counterpart listed for Support please mention @gitlab-com/support/managers
      • If there is no stable counterpart listed for Marketing please mention @cfoster3
  • Your GPM has been @mentioned so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.

Deprecation Milestone

15.9

Planned Removal Milestone

19.0

Links

Edited by 🤖 GitLab Bot 🤖