Deprecate Slack Slash Commands

Deprecation Summary

The Slack slash commands integration allows users to run common GitLab operations (such as creating issues, triggering CI/CD jobs, and viewing project information) directly from Slack using slash commands.

This integration is configured at the project level and is only available on GitLab Self-Managed and GitLab Dedicated instances.

Users will no longer be able to configure or use the Slack slash commands integration after it is removed in GitLab 19.0.

However, all slash command functionality remains available through the GitLab for Slack app, which provides a more secure integration method with the same capabilities.

Documentation

Am I impacted?

Your workflow may be impacted if you meet all the criteria below:

  1. You're on GitLab self-managed or GitLab Dedicated; AND
  2. Your instance administrator has configured the Slack slash commands integration; AND
  3. You actively rely on slash commands on Slack.

If this is the case for you, see the section below on what to do instead.

What to do instead

Install the GitLab for Slack app, which provides the same slash commands functionality.

Instance administrators can follow the installation instructions to set up the GitLab for Slack app.

The setup process takes approximately 20 minutes:

  • 10 minutes to create the Slack app
  • 10 minutes to complete the configuration in GitLab

Once installed, existing Slack automations that rely on slash commands should continue to work as before.

Next, disable the old integration at gitlab.example.com/admin/application_settings/integrations/slack_slash_commands/edit: under "Enable integration" uncheck the Active checkbox and click Save changes.

Product Usage

See https://gitlab.com/gitlab-com/Product/-/work_items/14352+

Breaking Change?

Yes

Affected Customers

Who is affected by this deprecation: GitLab.com users, Self-managed users, or Dedicated users? (choose all that apply)

  • GitLab.com
  • Self-managed
  • Dedicated

What pricing tiers are impacted?

  • GitLab Free
  • GitLab Premium
  • GitLab Ultimate

Deprecation Milestone

This deprecation will be announced in milestone: %18.7

Planned Removal Milestone

The feature / functionality will be removed in milestone: %19.0

Links

Checklists

Timeline

Rollout Plan

N/A: this does not affect gitlab.com.

Communication Plan

An internal slack post and a release post are not sufficient notification for our customers or internal stakeholders. Plan to communicate proactively and directly with affected customers and the internal stakeholders supporting them.

Internal Communication Plan This will have been documented in your breaking change request. You can use this checklist to track completion of these items.

External Communication Plan This will have been documented in your breaking change request. You can use this checklist to track completion of these items.

  • Customer announcement plan (timeline for notifications, audience, channels, etc)
  • Ensure you have approvals from legal and corp comms for any communication being sent directly to customers.
  • As soon as possible, but no later than the third milestone preceding the major release, ensure that the following are complete (for example, given the following release schedule: 17.8, 17.9, 17.10, 17.11, 18.0 – 17.9 is the third milestone preceding the major release).
  • On the major milestone:
    • The deprecated item has been removed. Add link to the relevant merge request.
    • If the removal of the deprecated item is a breaking change, the merge request is labeled breaking change.
    • Document the migration plan for users, clearly outlining the actions they need to take to mitigate the impact of the breaking change.

Development

Stakeholder Mentions

  • Product Designer @ProductDesigner
  • Tech Writer @eread
  • Software Engineering in Test @SET
  • Any other stable counterparts based on the product categories:
    • Add Sales/CS counterpart or mention @timtams
    • Support @mlockhart
    • Add Marketing counterpart or mention @martin_klaus
    • Add Corp comms if direct customer comms are needed @jmalleo
    • Product Security @ameyadarshan
    • Mention (in internal note) Customer Success Managers / Acount Managers / Solutions Architects for impacted customers

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.

References

Edited by Thiago Figueiró