Most engineering teams set up the Linear Slack integration, watch a few issue notifications land in #eng-updates, and call it done. That is a shame, because the integration does four distinct things and most teams have only switched on the first one.
The gap is real. When your development work happens in Linear and your team's conversations live in Slack, you create a gap. The notifications layer shows you that a gap exists - it does not close it. This post covers what the integration actually does, where it falls short by design, and what a good setup looks like once you know the whole picture.
What the Linear Slack integration actually does
The native Linear Slack integration is a two-way connection between a Linear workspace and a Slack workspace, built and maintained by Linear. It does four useful things, and most teams use only the first one.
The first is channel subscriptions. A Slack channel can subscribe to Linear events scoped by team, project, label, or status, and Slack receives a formatted message every time a matching event fires. This is the bit everyone configures in the first ten minutes and then forgets to revisit.
The second is the /linear slash command, which lets a Slack user create a Linear issue from inside a Slack thread, with the thread linked back to the issue for context.
The third is message shortcuts, which let you turn any Slack message into a Linear issue in two clicks. The fourth is URL unfurling, which renders Linear issue and project links inline with status, assignee, and the latest update.
URL unfurling is underrated. The moment you paste a Linear URL into Slack and your teammates can see status and assignee without clicking through, you eliminate a whole category of "hey what's the status on ENG-402?" messages.
The real friction: work that lives in Slack and never reaches Linear
Here is the pattern that burns the most time. A customer reports a bug in a shared Slack channel. Three people react with 👀. Someone says "I'll look into it." Two days pass. Nothing was filed.
The native Linear Slack integration is a good fit when issue creation from Slack is occasional and manual. However, many teams outgrow it once Slack becomes the primary channel for requests, bugs, and questions. The native integration does not automatically create issues from every relevant Slack message.
This limitation is what drives teams to explore automation tools or Slack-native workflow platforms later on.
The fix Linear built for this is Linear Asks. Linear Asks is a feature that integrates Slack with Linear, allowing users to convert Slack messages into actionable tasks or issues in Linear. The key difference from the base integration: once enabled, anyone can create an Ask to send their request to the relevant Linear team via Slack, even if they don't have a Linear account.
When an Ask is created for a Linear team, it starts in the team's Triage for review, prioritization, and assignment. Asks created from Slack keep a synced comment thread between Linear and Slack, so replies in either place stay connected.
That last part matters more than it sounds. Engineers can update a thread in Linear and the person who reported the issue in Slack sees the reply - without a Linear account, without context-switching. When people in your company report issues in Slack, syncing threads is a great way to keep them in the loop regardless of whether they're in your Linear workspace.
Beagle in action#ask-product, 2:17pmHow to configure it so it actually sticks
Start at Linear's Settings → Integrations → Slack and do four things in order:
Scope your channel subscriptions. Pick one or two dedicated channels (
#linear-critical,#eng-releases) rather than routing all team events to#general. Refine notification filters in Linear settings to only send alerts for specific issue types or priority levels.Enable message shortcuts workspace-wide. Completing this step enables creating issues from Slack, message actions, and expandable links for every member of the workspace. This is a single toggle that most admins miss.
Add issue templates to the Slack integration. Admins can make up to 10 issue templates available in the Slack integration, which any Linear members in the Slack workspace can view and apply during issue creation. A "Bug Report" template with required fields for reproduction steps cuts the back-and-forth on under-specified issues significantly.
Turn on Linear Asks for intake channels if people outside your engineering team report issues in Slack. Linear Asks lets any member of your Slack workspace create an Ask in connected channels and DMs - no Linear account required - via the
/askcommand, More actions menu, or ticket emoji. Note: Asks requires a Business or Enterprise plan.
The newer addition worth knowing about: you can connect Linear's MCP server to Slackbot so it can access your Linear data when you ask it questions in Slack. A Slack admin adds Linear as a custom MCP server in Slackbot's connector settings. Once wired up, Slackbot can call tools to list or find issues across your workspace filtered by team, assignee, project, label, status, or priority, and can create or update an issue - setting title, team, assignee, project, labels, priority, and status. That is a meaningful step beyond what the base integration provides.
The one thing the integration cannot do on its own
The integration surfaces information and provides hooks for creating issues. It does not write the issues for you.
This is where the real time cost hides. Filing a good Linear issue from a Slack thread - pulling the right context, picking the right team, setting priority, adding a reproduction description - takes a few minutes per ticket. Multiply that across a 20-person team where anyone might be the one who fields a request, and the friction is real.
Linear Asks helps organizations manage internal requests that would otherwise be scattered across chat, email, and ad hoc forms. But even Asks requires someone to frame the request well. Configuring templates with concrete instructions, placeholders, and checkboxes helps standardize and streamline intake
- though the person submitting still has to fill them in.
An AI teammate in the channel can read the thread, draft the issue with the right fields pre-populated, and post it for a quick human approve before it lands in Triage. The issue gets filed, the thread gets linked, and nobody had to open a second tab.
Beagle in action#ask-eng, 10:03amLinear Slack integration: common questions
What does the Linear Slack integration actually do?
The Slack integration makes it easy to create, update, and view Linear issues from Slack. Notifications and synced threads keep colleagues in the loop on projects and issues.
Concretely, it offers channel subscriptions for event notifications, a /linear slash command for issue creation, message shortcuts to file an issue from any Slack message, and URL unfurling for inline issue previews.
What is Linear Asks and how is it different from the base integration?
Linear Asks is designed for internal requests that might otherwise get lost across chat threads, shared inboxes, and ad hoc forms. It's especially useful for engineering teams receiving bug reports from non-technical teammates, IT and support teams handling access requests, and product teams collecting feature requests. The key difference: Asks works for Slack users who have no Linear account.
Do you need a Linear account to create issues from Slack?
For the base integration, yes. Only Linear users in your Slack workspace can create issues with this integration. If you want to allow non-Linear users in your Slack workspace to create issues, consider using Asks instead. Asks is available on Business and Enterprise plans.
How does thread sync work between Slack and Linear?
When you create issues from Slack, the comment thread in Slack will be bidirectionally synced with a thread in the issue. This is particularly useful for keeping users reporting issues informed even if they don't have a Linear account. In addition to syncing comments, the synced thread in Slack will be updated when the issue is completed or cancelled.
Can you query Linear from Slack without opening the app?
Yes, if you connect Linear's MCP server to Slackbot (available now - a Slack admin adds it in connector settings). Once connected, Slackbot can call tools to find issues across your workspace, filtered by team, assignee, project, label, status, priority, or cycle. This is separate from the base integration and requires Slackbot's MCP connector feature.