Skip to content

Run with Linear

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: Teams already living in Linear
  • Time: After a Native backlog exists
  • Plan: Connected is Enterprise / design-partner — not Team. Same as Jira.
  • Connect Linear on an Enterprise workspace from /org/integrations.
  • Push a planned backlog and execute in Linear.
  • Linear is the system of record and Connected is actually enabled.
  • Enterprise Connected. Team is not enough.
  • A GrowthOS backlog worth pushing.
  • /org/integrations
  • Read Run with Jira for the shared policy (agents, Slack notifications).
  1. Finish Native planning first.
  2. Open /org/integrations and choose Linear (not Jira). Skip Jira-only fields.
  3. Map to Linear team/project as the wizard asks. Push work.
  4. Execute in Linear. Confirm sync back. Keep agents off synced status writes.
  • Linear holds execution. GrowthOS holds the plan and synced status.
  • Asana, ClickUp, and GitLab are the same pattern — swap the tracker, keep the gates.
  • Filling Jira site URL on a Linear connect.
  • Expecting Connected on Team.