Run with Jira
Overview
Section titled “Overview”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 / time / plan
Section titled “Who / time / plan”- Who: Teams already living in Jira
- Time: After a Native backlog exists
- Plan: Connected is Enterprise / design-partner — not Team.
What you can do here
Section titled “What you can do here”- Connect Jira from
/org/integrationson an Enterprise workspace. - Push a planned backlog (existing vs new Jira project, epic/story mapping).
- Watch status sync back into GrowthOS.
When to use
Section titled “When to use”- Leadership requires Jira as the system of record for execution.
- You already have an Enterprise / design-partner Connected flag.
Prerequisites
Section titled “Prerequisites”- 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.
Where to find it
Section titled “Where to find it”/org/integrations- Integrations overview in these docs.
Step-by-step
Section titled “Step-by-step”- Finish Native planning (Idea Lab or existing-product wave) so the backlog is real.
- Open
/org/integrationsand start Jira. Enter the site URL. - Choose existing Jira project vs create new. Map epics/stories/sub-tasks.
- Optionally match a Jira sprint. Push the work.
- Execute in Jira. Confirm statuses appear back in GrowthOS.
- If you also use a coding agent, point it at Native-only tickets — never synced status writes.
What success looks like
Section titled “What success looks like”- Jira holds execution. GrowthOS still holds the plan and synced status.
- No agent errors from
TASK_SYNCED_READ_ONLYbecause you did not fight sync.
Tips & best practices
Section titled “Tips & best practices”- 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.
Common mistakes
Section titled “Common mistakes”- 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.