Linear Slack Integration: Setup & Notifications
Connect Linear to Slack to create issues from messages, keep comments in sync, and receive relevant updates. Start with workspace setup, then configure notifications for each audience.
TL;DR
Linear's native Slack integration lets you create issues from messages, receive notifications for status changes, and link Slack channels to Linear teams. This guide covers setup, configuration, and best practices for getting the most out of the integration. Native synced threads can retain the discussion alongside an issue; additional product requirements still need to be documented by your team.
Why Connect Slack to Linear
Slack is where product conversations happen. Linear is where work is tracked. Without a connection, bugs reported in Slack need to be manually copied into Linear, and status updates in Linear need to be manually shared in Slack. The integration reduces manual copying, but your team still needs to decide which discussions become issues.
Linear's Slack integration is one of the cleanest in the issue tracker space. Issue creation from messages is fast, link previews are rich, and notification configuration is granular. For teams using both tools, this integration is essential.
How to Connect Slack to Linear: 5 Steps
Step 1: Install the Integration
Go to Linear Settings > Integrations > Slack. Click “Connect.” Authorize Linear to access your Slack workspace. You need a Linear admin (or owner on Enterprise) and any app approval required by your Slack workspace. Once connected, the Linear bot appears in your Slack workspace.
Step 2: Configure Notifications
In Linear Settings > Personal > Notifications, configure personal Slack notifications. Personal notifications arrive as DMs from Linear. Configure team channel notifications separately in the team settings. Keep both focused to avoid notification fatigue.
Step 3: Link Channels to Teams
In Linear, open the team's Slack notification settings and choose a channel. When linked, you can configure whether new issues post to the channel, and whether status updates or comments appear there. Personal DM settings are managed separately. This keeps team-relevant updates in the team channel.
Step 4: Create Issues from Messages
Hover over any Slack message, click the three-dot menu (More Actions), and select Connect to apps > Create new issue. A modal opens with the message text in the description. Set the team, project, priority, labels, and assignee. Click Create. The issue is created in Linear and a link is posted back in the Slack thread. The original Slack message is also linked in the Linear issue.
Step 5: Use Link Previews
When someone pastes a Linear issue URL in Slack, it automatically unfurls with a rich preview showing the issue title, status, assignee, and priority. This eliminates the need to switch to Linear to see issue details. Public-team issue previews support actions such as assigning and commenting; private-team links do not unfurl.
Troubleshoot Missing Threads or Previews
Invite Linear to a private channel before using synced threads. Thread sync is not supported in direct messages. For missing link previews, check Slack's Messages & Media preferences and Linear's integration settings. Test with a public-team issue; private-team issue links are intentionally excluded from previews.
Check Linear's Slack documentation for current permissions, notification settings, and troubleshooting instructions.
Tips
- Use a dedicated #bugs or #feature-requests channel and train the team to create Linear issues from messages in those channels rather than from general conversation.
- Set up notification rules so only relevant updates reach Slack. Sending every status change to a channel creates noise that people learn to ignore.
- Use Linear's Triage feature alongside Slack. Messages become triage items that the PM reviews and accepts or declines into the backlog.
- Add context to issues after creation. A Slack message is a starting point, not a complete ticket. Add acceptance criteria and priority in Linear after creating.
How Vantage Makes This Better
Vantage helps teams turn collected product context into PRDs, requirements, and tickets. Add the relevant discussion as project context, review the generated specification, and push approved tickets to Linear when the project is connected.
Vantage also maintains two-way sync with Linear, so ticket status changes in Linear are reflected in Vantage and vice versa. Review sync changes before applying them to keep the product specification and delivery work aligned.