Skip to content

Design: Slack application link unfurling states

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

Problem

There are a large number of GitLab links shared every month in Slack across all of GitLab's users. This number has almost doubled year over year. We should update our link previews to provide richer context while making them more actionable.

As a first iteration we should leverage the Slack App unfurling which will provide more control over the content layout and lay the groundwork for adding interactivity to unfurls (i.e. Being able to retry a failed job from Slack, etc.).

The design proposals in this issue also take into consideration current inconsistencies with how GitLab information is displayed. For example: Slack notifications, slash commands, and unfurled links should show same content when displaying issue .

⚠️ All proposed designs in this issue assume links being shared are Public. This issue does not address handling private unfurls. For that, please see issue: Unfurl private GitLab links shared in Slack workspace.

Proposal (1st priority)

Lower priority Stretch

  • Commit link
  • Epic link
  • GitLab user link
  • Line of code link (#215143)
  • Design management link
  • Board link

Resources

Edited by 🤖 GitLab Bot 🤖