ChatOps slack intergation doesn't work for me

I am using SaaS
Slack integration ChatOps works for all my colleagues but not for me. I couldn’t find any permissions/configuration differences. The only difference is that I joined the company later than others maybe it is related to some bug that appeared in Gitlab recently.

What we have configured:

  1. Gitlab project integration is configured as said in the documentation

  2. GitLab repository with .gitlab-ci.yml from ChatOps documentation page

  3. My gitlab user’s is a group Owner role and slack user’s is Workspace admin

  4. I authenticated my Slack user in Gitlap app when I did first /gitlab command in slack. In my Gitlab profile User settings -> Chat I see this:

  5. I try /gitlab slack-test run ls command in Slack I get this error immediately:
    Sorry, this chat service is currently not supported by GitLab ChatOps.

but in the Gitlab repository Pipelines I see successfully created and completed Job

I tried a lot of things, use different Slack workspaces, different Gitlab users etc. Nothing helps

We’re experiencing something similar. However, I am the one who added the integration on one of our repositories and I don’t experience issues, only others in my organization.

When I run the commands, they return. But anyone else (independently of being an Owner in the GL repository or not) gets the error you are seeing.

1 Like

seems like it worth creating a gitlab issue for this,

We’re experiencing the same issue with our self-managed GitLab instance. Its a bit strange is that when the Authorization happens the Project and Service in the User Profile → Chat accounts are set to Not applicable. Atleast I know in the GitLab SaaS they have removed the Slack Slash Commands Integration infavor of GitLab Slack App.

@leviwilson It works for you because you already have atleast one chat accounts already active under User Profile → Chat accounts. If you remove all of the Chat accounts and then try Connecting Slack with GitLab you would face the same issue.

1 Like

In our GitLab Self-Managed Instance, this issue was resolved after enabling use_response_url_for_chat_responder Feature Flag. Thanks to GitLab Support Team.