Skip to content

Run with Jira

Default execution is Native. Connected is an Enterprise overlay: you still plan in GrowthOS, then push work to Jira and execute there. Status syncs back. Slack is notifications only.

Jira-specific UI: site URL; use an existing Jira project or create one; map to Epics / Stories / Sub-tasks; optionally match a Jira sprint. Linear, Asana, ClickUp, and GitLab use the same Connected pattern; those Jira-only fields are N/A there.

Coding agents work Native MCP tickets. They must not overwrite synced status (TASK_SYNCED_READ_ONLY). If the team executes in Jira, keep agents off those synced items or expect read-only status.

  • Who: Teams already living in Jira
  • Time: After a Native backlog exists
  • Plan: Connected is Enterprise / design-partner — not Team.
  • Connect Jira from /org/integrations on an Enterprise workspace.
  • Push a planned backlog (existing vs new Jira project, epic/story mapping).
  • Watch status sync back into GrowthOS.
  • Leadership requires Jira as the system of record for execution.
  • You already have an Enterprise / design-partner Connected flag.
  • Enterprise Connected enabled. Team plan is not enough.
  • A GrowthOS backlog worth pushing — do not connect an empty project.
  • Jira site URL and permission to create or select a project.
  • /org/integrations
  • Integrations overview in these docs.
  1. Finish Native planning (Idea Lab or existing-product wave) so the backlog is real.
  2. Open /org/integrations and start Jira. Enter the site URL.
  3. Choose existing Jira project vs create new. Map epics/stories/sub-tasks.
  4. Optionally match a Jira sprint. Push the work.
  5. Execute in Jira. Confirm statuses appear back in GrowthOS.
  6. If you also use a coding agent, point it at Native-only tickets — never synced status writes.
  • Jira holds execution. GrowthOS still holds the plan and synced status.
  • No agent errors from TASK_SYNCED_READ_ONLY because you did not fight sync.
  • Same pattern for Linear / Asana / ClickUp / GitLab — see Run with Linear for the short sibling.
  • Stay Native if you are not Enterprise. Do not treat the integrations page as a Team feature.
  • Connecting Jira before any backlog exists.
  • Telling the sprint agent to mark synced Jira issues DONE.
  • Expecting Connected on Team because you have five seats.