Linear Integration
Turn feedback into Linear issues. When someone submits feedback, an issue is created in your chosen team with the message, screenshots, priority, and a link back to your site.
Setup
Step 1: Connect Linear
- Go to Project Settings > Integrations > Linear
- Click Connect to Linear
- Authorize SimpleCommenter in the popup
- Grant access to your Linear workspace
Step 2: Choose a Destination
After connecting, select where issues should be created:
- Team — pick which Linear team will receive issues (required)
- Project — optionally assign issues to a project (cross-team grouping)
In Linear, every issue belongs to a team. Projects are optional groupings that can span multiple teams — useful for initiatives like "Q1 Launch" or "Website Redesign".
Step 3: Choose a Routing Mode
Simple Mode
All feedback goes to one team (and optionally one project). Select from the dropdowns.
Good for small teams or projects where all feedback goes to the same place.
Advanced Mode
Create routing rules that send feedback to different teams based on conditions. For example, route design feedback to the Design team and bugs to Engineering.
See Routing Rules below for the full list of options.
New projects default to Simple mode. You can switch between modes at any time without losing your configuration.
Step 4: Enable the Integration
Use the toggle in the header to turn the integration on. You can disable it at any time to pause syncing without disconnecting or losing your settings.
Where to Configure
You can set up Linear in two places:
Project Settings
Go to Project > Settings > Integrations > Linear
- Applies only to this specific project
- Overrides any default settings
Default Settings
Go to Default Settings > Integrations > Linear
- Applies to all new projects automatically
- Useful if you want every project to create issues in the same team
Project-level settings always take priority. If you configure Linear for a specific project, that configuration is used instead of the defaults.
Routing Rules
In Advanced mode, each rule has four parts:
Triggers
Choose which events fire the rule:
- Name
New comment- Type
- Trigger
- Description
Someone submits feedback
- Name
Reply- Type
- Trigger
- Description
Someone replies to existing feedback
- Name
Status update- Type
- Trigger
- Description
A comment's status or priority changes
New rules default to New comment and Reply enabled.
Conditions
Filter which feedback matches the rule. No conditions means the rule matches everything. Multiple conditions use AND logic — all must match.
- Name
Priority- Type
- is, is not
- Description
Low, Normal, High, Urgent
- Name
Status- Type
- is, is not
- Description
To Do, In Progress, Review, Rework, On Hold, Blocked, Done, Cancelled, Won't Fix
- Name
Commenter role- Type
- is, is not
- Description
Client, Team Lead, Workspace Admin
- Name
Tagged user- Type
- includes
- Description
Any team member
- Name
Page URL- Type
- is, contains, starts with
- Description
Text (e.g.
/blog,/pricing)
Destination
Each rule sends matching feedback to a specific Linear team.
Examples
- Client feedback to a dedicated team: Condition = "Commenter role is Client" → Team: Client Support
- Bugs to engineering: Condition = "Page URL contains /app" → Team: Engineering
- High priority alerts: Condition = "Priority is High or Urgent" → Team: Urgent Triage
What Gets Synced
New Feedback → Linear Issue
When someone submits feedback, an issue is created with:
Issue title:
#123 | Button not working on checkout page
Issue description includes:
- The feedback message
- Who submitted it (name, email)
- Date and time
- Page URL
- Status and priority
- Link back to SimpleCommenter
Screenshot:
If the user captured a screenshot, it's attached to the issue via Linear's attachment system and embedded in the description as an image.
Priority:
Linear's built-in priority field is set automatically:
- Name
Low- Type
- Linear: Low (4)
- Description
Low priority
- Name
Normal- Type
- Linear: Medium (3)
- Description
Normal priority
- Name
High- Type
- Linear: High (2)
- Description
High priority
Workflow state:
New issues are created in the team's default workflow state (typically "Backlog" or "Triage"), matching the feedback's current status.
Replies → Issue Comments
When you reply to feedback in SimpleCommenter, a comment is added to the Linear issue with the reply text and any attachment links.
Status & Priority Updates
When you change status or priority in SimpleCommenter:
- The issue's workflow state is updated to match (mapped to the closest state type)
- The issue's priority level is updated
- A comment is added to the issue describing the change
Status mapping:
SimpleCommenter statuses are mapped to Linear workflow state types:
- Name
To Do- Type
- unstarted
- Description
Maps to the team's unstarted state
- Name
In Progress- Type
- started
- Description
Maps to the team's started state
- Name
Review- Type
- started
- Description
Maps to the team's started state
- Name
Done- Type
- completed
- Description
Maps to the team's completed state
- Name
Cancelled- Type
- cancelled
- Description
Maps to the team's cancelled state
Enabling and Disabling
The toggle in the integration header lets you pause syncing without disconnecting. Your team selection and routing rules are preserved.
- Enabled: Feedback syncs to Linear as configured
- Disabled: No issues are created or updated. Settings stay intact
Troubleshooting
Issues Not Creating?
- Check the toggle — Make sure the integration is enabled (not just connected)
- Check authorization — Verify Linear shows as connected
- Verify team selection — A team must be selected
- Check routing rules — In Advanced mode, at least one rule must be active with matching conditions
- Re-authorize — Click Disconnect, then Connect again to refresh the token
Priority Not Mapping?
Linear uses a numeric priority scale (1=Urgent, 2=High, 3=Medium, 4=Low). SimpleCommenter maps automatically: Low→4, Normal→3, High→2.
Disconnecting
- Go to Integrations > Linear
- Click Disconnect
- Confirm the disconnection
Existing Linear issues are not deleted when you disconnect. They remain in your workspace.