Linear

Linear can be connected twice, and each connection does a different job.

Connection	Who connects	What it does
Workspace	An owner or admin	Registers signed webhooks for Issue, Comment, and Project events and keeps issues you imported current. It never imports issues on its own.
Personal	Any member (not viewers)	Lets you browse your Linear teams, projects, and issues and import the ones you pick. Nothing is pulled until you ask.

Connect the workspace

Open Data Sources → Available.
On the Organization entry for Linear, select Add connection.
Approve the requested scopes in Linear.
Return to yggy and check the connection status.

The OAuth flow reads the connected workspace name. yggy then registers a webhook for Issue, Comment, and Project events.

Connect your own account

Open Data Sources → Available, or the source menu in the upload dialog.
On the Personal entry for Linear, select Connect.
Approve read access in Linear.

Your account is never used by anyone else in the organization. Disconnecting it only removes your connection.

Import issues

Open the upload dialog and choose Linear.
Pick a team, then a project or an issue. Use the search box to find issues by title.
Select the issues and import them.

Each issue becomes a Markdown document with its identifier and title, state, assignee, labels, description, and comments. Importing the same issue again returns the document you already have.

Requested scopes

Connection	Scope	Purpose
Workspace	`read`	Read workspace data and validate the connection.
Workspace	`issues:create`	Support issue-creation capabilities.
Workspace	`admin`	Create and remove the Linear webhook.
Personal	`read`	Browse and read your issues.

A personal connection never asks for admin. The workspace connection can also store an optional comma-separated team filter. The filter does not limit what members import with their own connection: they see whatever their own Linear account can see.

Test and reconnect

Use Test connection on the workspace connection to validate its access token with Linear’s viewer query. Reconnect after token revocation, a scope change, or a lost webhook.

Disconnecting the workspace makes a best-effort request to remove the Linear webhook, then removes the local credentials and connection.

Keeping imported issues current

When an issue you imported changes in Linear, or someone comments on it, yggy updates the imported copy and extracts it again. Issues you never imported are not added: import them from Data Sources first. If you delete an issue in Linear, its imported copy moves to the trash and its facts leave the graph; you can restore it from the trash. Archiving an issue in Linear counts as a change, so the imported copy is updated, not removed.

The workspace connection does this work, so an admin needs to connect it. It updates every imported copy of an issue in the organization, including copies members imported with their own account. A personal connection is never used for this. If the workspace connection has a team filter, issues outside that filter are left as they are.

The Connection card on the connection’s settings page shows when the connection last synced and whether the last sync ran into a problem. Re-extraction uses credits like any other re-extraction; when credits are used up, yggy leaves the imported copy as it is and updates it once credits are available.

Limits

Removal works from Linear’s delete event only. If yggy misses that event, the imported copy stays until you delete it.
yggy also checks Linear every few minutes in case an event was missed. That check looks back at most 14 days, and the first check of a connection only marks the starting point, so it does not pick up older changes.
A change that does not alter the imported text, such as a priority edit, does not trigger a new extraction.
If an imported issue failed to extract, the next change to that issue tries again.
Sync only refreshes documents that are visible to the whole organization.

See Provider webhooks for the exact receive behaviour.