Run with Linear
Overview
Section titled “Overview”Linear follows the same Connected overlay as Jira, Asana, ClickUp, and GitLab: plan in GrowthOS, connect at /org/integrations, execute in the tracker, status syncs back. Agents must not overwrite synced status (TASK_SYNCED_READ_ONLY).
Jira-only UI does not apply: site URL, existing-vs-new Jira project, Epics/Stories/Sub-tasks mapping, matching Jira sprint. Use Linear’s own project/team fields in the connect wizard instead.
Who / time / plan
Section titled “Who / time / plan”- Who: Teams already living in Linear
- Time: After a Native backlog exists
- Plan: Connected is Enterprise / design-partner — not Team. Same as Jira.
What you can do here
Section titled “What you can do here”- Connect Linear on an Enterprise workspace from
/org/integrations. - Push a planned backlog and execute in Linear.
When to use
Section titled “When to use”- Linear is the system of record and Connected is actually enabled.
Prerequisites
Section titled “Prerequisites”- Enterprise Connected. Team is not enough.
- A GrowthOS backlog worth pushing.
Where to find it
Section titled “Where to find it”/org/integrations- Read Run with Jira for the shared policy (agents, Slack notifications).
Step-by-step
Section titled “Step-by-step”- Finish Native planning first.
- Open
/org/integrationsand choose Linear (not Jira). Skip Jira-only fields. - Map to Linear team/project as the wizard asks. Push work.
- Execute in Linear. Confirm sync back. Keep agents off synced status writes.
What success looks like
Section titled “What success looks like”- Linear holds execution. GrowthOS holds the plan and synced status.
Tips & best practices
Section titled “Tips & best practices”- Asana, ClickUp, and GitLab are the same pattern — swap the tracker, keep the gates.
Common mistakes
Section titled “Common mistakes”- Filling Jira site URL on a Linear connect.
- Expecting Connected on Team.