Support and issues / QA preview
Linear + EarShots
The EarShots Linear integration is designed to turn a selected developer friction mention into an issue in your team's Linear workspace. Review the ticket, choose a team and explicitly authorize creation. The initial adapter is in QA; connecting does not publish replies or change the source conversation.
Open connection setupWhat can you do with this integration?
- List accessible Linear teams
- Preview a ticket using the saved mention and source link
- Queue explicit issue creation and recover its external result without blind retries
Worked examples
These examples explain the QA adapter. They are not customer results or certification evidence.
Send a friction report to engineering
- Input
- Illustrative example: a saved mention describes a timeout during an SDK setup.
- Action
- Preview the source quote and URL, select a test team, then authorize the exact ticket in EarShots.
- Expected result
- One Linear issue with its saved external link. The report does not become a confirmed bug merely because it was exported.
Recover a slow issue request
- Input
- An authorized create operation times out after dispatch.
- Action
- Inspect the same operation ID. The worker checks its deterministic Linear issue ID before creating anything again.
- Expected result
- The existing issue is recovered, or the operation remains held for reconciliation. The client does not submit a second create with a new key.
Fields and data direction
EarShots sends the explicitly approved ticket to the selected Linear team.
| Field | Meaning |
|---|---|
| Title | Reviewed ticket title |
| Description | Source-backed ticket Markdown |
| Team | Explicitly selected accessible team UUID |
| External result | Linear issue ID and URL |
How to connect Linear
A Linear account authorized to read teams and create issues in the chosen team. Configure the minimum provider scopes required for these operations. EarShots workspace owners and admins authorize writes.
- Open setup, sign in to EarShots and choose your workspace.
- An owner or admin reviews the requested provider access and completes consent. QA setup must first be enabled for this provider.
- Select the exact Linear team to use. Other resources are not automatically imported.
- Create a preview and run a small test. Review and authorize the exact ticket in the app before issue creation.
- Inspect the saved operation result. Manage or disconnect the account from workspace integrations.
Limits and recovery
A developer report is evidence of a reported experience, not confirmation of a product defect. The selected customer team is the destination. Existing format_ticket remains read-only. Issue creation is separate from reply approval, public posting, assignments and issue resolution.
Queued work follows the workspace worker schedule. If authorization expires, reconnect and reselect the resource. Keep the same operation and idempotency key when checking a retry. Disconnect blocks new work; an external request already in progress can still finish.
Common questions
Can I use this through MCP, CLI or the API?
The QA implementation shares the same workspace authorization and operation service across all four surfaces. Start setup from a tool or command, then complete provider consent in your browser. Machine requests do not receive provider credentials.
Is this available now?
This adapter is in QA. Setup depends on provider configuration, your workspace permissions and plan. Live availability will be recorded after account authorization and workflow tests pass.
Does connecting authorize publishing or marketing sends?
No. Connecting grants only the configured provider permissions. Workflow execution, content approval, publication and marketing consent are separate decisions.
Provider reference: Linear developer documentation. Adapter behavior requires live verification before launch.