Slack application to GitLab connection interactions

Problem

The current version of the GitLab, Slack slash command app does initially prompt the Slack user to connect their GitLab, however once connected, the app receives no further updates regarding the Slack user's connection to GitLab. For example, if an already connected Slack user were to navigate to https://gitlab.com/-/profile/chat_names and remove their connection, the Slack application still assumes that the accounts are connected and fails with the message: GitLab error: project or alias not found when trying to use any of the slash commands.

This issue will focus on identifying the main connection flows and create proposals.

Assumptions

  • GitLab Slack app is already installed on your Slack workspace

JTBD

  1. I want to be able to connect my Slack account with my GitLab account so I can get updates from GitLab projects that I am a collaborator in.
  2. I want to_ be able to connect a new GitLab project to my Slack account so I can get new updates from the GitLab project that I was recently added to.
  3. I want to_ be able to see a list of all groups/projects that my Slack account has linked so I can manage .
  4. I want to disconnect my Slack account from an existing GitLab project so that I no longer need to receive updates from it.

Proposal summary

  1. Regardless whether a Slack user has been prompted to connect their GitLab account, we should make it easy for anyone in the Slack workspace to authenticate by adding new /gitlab connect & /gitlab disconnect commands
  2. We should show the connection status within Slack by adding a "Connect GitLab account" / "Disconnect GitLab account" depending on the state
  3. Update https://gitlab.com/-/profile/chat_names to support success and error messages
  4. Update https://gitlab.com/-/profile/chat_names to support grouping by group/project
Edited by Libor Vanc