Design: Slack application link unfurling states
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 .
Proposal (1st priority)
Stretch
Lower priority-
Commit link -
Epic link -
GitLab user link -
Line of code link (#215143) -
Design management link -
Board link