Linear Integration
Connect Jetson to Linear to create issues directly from customer feedback. Jetson also syncs status changes bidirectionally—when you move an issue in Linear, Jetson updates automatically.
Setting up Linear
Connect your workspace
- Go to Settings in Jetson
- Under Destinations, click Connect Linear
- You'll be redirected to Linear to authorize
- Grant Jetson access to your workspace
- You'll be returned to Jetson
What Jetson can do
When connected, Jetson can:
- Create issues in your Linear workspace
- Read teams, projects, and workflow states
- Sync status changes bidirectionally
Jetson cannot:
- Delete issues
- Access private information beyond issue tracking
- Modify your Linear workspace settings
Permissions requested
Jetson requests these Linear scopes:
| Scope | Why we need it |
|---|---|
| read | Query teams, projects, and workflow states |
| write | Update issue status for two-way sync |
| issues:create | Create new issues from Jetson |
| admin | Set up webhooks for two-way status sync |
Configuring products
Select a team
After connecting Linear, configure each product:
- Go to Settings > Products
- Select your product
- Choose Linear as the output destination
- Select which Linear team to create issues in
- Optionally select a project within that team
- Save your changes
Each product can use a different team or project.
Configure state mapping
Jetson maps Linear workflow states to Jetson statuses. The defaults work for most setups:
| Linear state type | Jetson status |
|---|---|
| Backlog | Inactive |
| Started (In Progress) | Active |
| Completed (Done) | Resolved |
| Canceled | Deferred |
To customize the mapping:
- Open your product settings
- Find the State Mapping section
- For each Linear state, choose the Jetson status
- Save your changes
Custom mappings let you handle workflows with multiple "In Progress" states or custom state types.
Creating Linear issues
From a bug or feature
- Open any bug or feature in Jetson
- Click Create Linear Issue
- Review the generated issue content
- Confirm to create
The issue appears in your configured Linear team and project.
What's included
Linear issues include:
- Title — From Jetson's analysis
- Description — Summary of customer feedback
- Customer count — How many customers reported this
- Link back to Jetson — For full context
Two-way status sync
How it works
When you change an issue's status in Linear, Jetson updates automatically:
- Move to "Done" in Linear → Jetson marks as Resolved
- Move to "In Progress" → Jetson marks as Active
- Move to "Backlog" → Jetson marks as Inactive
- Cancel in Linear → Jetson marks as Deferred
The sync works the other way too. Change a work item's status in Jetson and the Linear issue updates.
Requirements
Two-way sync requires:
- Admin role in Linear (to create webhooks)
- Linear connected with full permissions
- State mapping configured for your product
If you connected without admin access, you'll see a warning. Reconnect with an admin account to enable two-way sync.
Disconnecting
To disconnect Linear:
- Go to Settings
- Find Linear under Destinations
- Click Disconnect
What happens:
- No new issues can be created
- Two-way sync stops
- Existing Linear issues remain
- Links in Jetson still work
- You can reconnect anytime
Reconnecting Linear
If Linear stops working or you need to change accounts:
- Disconnect the current connection (see above)
- Click Connect Linear again
- Authorize with your Linear account
- Reconfigure your products if needed
Common reasons to reconnect:
- Changed Linear workspaces
- Token expired or was revoked
- Need to grant additional permissions
- Switching to an admin account for two-way sync
Multiple products
One connection, many products
A single Linear connection serves your entire organization:
- Connect Linear once
- Configure each product with its own team/project
- Each product creates issues in its configured location
Different teams per product
Products can target different Linear teams:
- Support product → Engineering team
- Sales product → Product team
- Enterprise product → Enterprise team
Configure this in each product's settings.
Next steps
- Understanding Work Items — Learn about bugs and features before creating issues
- GitHub Integration — Alternative issue destination
- How Classification Works — Understand how Jetson categorizes feedback