[go: up one dir, main page]

Skip to content

Slack app breaks after changing channel name

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

Currently, the Slack app (on SaaS) integration works when following the set up instructions. However, when it seems if the Slack channel name is updated in Slack the integration is broken and an error for "Connection fail. Check your integration settings. Unable to post to #slacmchannelname, please add the GitLab Slack to any private Slack channels.

Steps to reproduce

  1. Integrate Slack app and add to a channel
  2. Change the Slack channel
  3. Go to Settings > Integrations page, then error should show up

Example Project

What is the current bug behavior?

  • Error for "connection failed" when Slack channel name changes

What is the expected correct behavior?

  • Slack integration should connect seamlessly even if the channel name changes

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:env:info\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`)

(For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)

(we will only investigate if the tests are passing)

Possible fixes

Edited by 🤖 GitLab Bot 🤖