Jira Cloud is Roadmap OS's most-used integration. Two-way sync keeps your roadmap and your engineering backlog aligned without manual reconciliation.

What syncs

From Roadmap OS	To Jira
Initiative	Epic
Initiative status change	Epic status update
Initiative date range	Epic due date
Initiative assignee	Epic assignee

From Jira	To Roadmap OS
Epic status change	Initiative status update
Issue completion under an epic	Plan task progress (if linked)
Comment on epic	Comment on initiative

You configure direction (one-way / two-way) and frequency (real-time / 15-min / hourly / daily).

Setup

Settings → Integrations → Jira → Connect

Click Connect
OAuth flow opens — sign in to your Atlassian account
Choose the Jira site to connect
Choose the projects to sync (you can sync multiple projects)
Click Authorize

Setup takes ~5 minutes. Existing Jira epics auto-import as Roadmap OS initiatives within 1-2 minutes after connect.

Configure sync direction

After connecting, Integrations → Jira → Configure:

Two-way sync (default) — both systems stay in sync
One-way: Jira → Roadmap OS — Jira is canonical; Roadmap OS reflects
One-way: Roadmap OS → Jira — Roadmap OS is canonical; pushes to Jira

For most teams: two-way is correct. The PM updates initiatives in Roadmap OS; engineers update issues in Jira; both flow.

Status mapping

Roadmap OS uses 5 statuses. Jira workflows are usually different. Configure → Status Mapping:

Roadmap OS status	Default Jira status mapping
Strategy	"To Do" / "Open" / "Backlog"
In Progress	"In Progress" / "In Development"
Released	"Done" / "Released" / "Closed"
At Risk	(none — flag in Roadmap OS only)
Delayed	(none — flag in Roadmap OS only)

If your Jira project uses custom statuses (e.g., "Code Review," "QA"), map them to the closest Roadmap OS status.

Tip: "At Risk" and "Delayed" are PM-side flags that don't need Jira equivalents. Update them in Roadmap OS based on your judgment, not on Jira state.

Sync frequency

Configure → Sync Frequency:

Real-time (webhook-based) — within 30 seconds — recommended for most teams
Every 15 minutes — useful for very large projects (1000+ issues)
Hourly — minimal API usage; good for low-activity projects
Daily — sleep mode

PR linking via #roadmap-{id}

If you also use GitHub:

Tag a PR title with #roadmap-123 (where 123 is the initiative ID)
The PR appears as a linked artifact on the initiative
Merging the PR doesn't auto-change status; that's still controlled by Jira / Roadmap OS

What happens to existing Jira epics on connect

Existing epics in your selected projects auto-import as Roadmap OS initiatives. Mapping:

Epic name → Initiative name
Epic description → Initiative description
Epic assignee → Initiative owner
Epic status (mapped) → Initiative status
Epic due date → Initiative end date

You can review and edit each imported initiative before publishing to your team.

What doesn't sync

Sub-tasks under epics — these stay in Jira; they map to Plan tasks if you link a Plan to the initiative
Comments older than the connection date — only new comments sync
Custom fields — only standard Jira fields sync; custom fields stay in Jira
Attachments — link references sync, not the file content

Troubleshooting

Sync seems frozen:

Settings → Integrations → Jira → click "Force Sync Now"
Check Jira API rate limits in Atlassian admin
Email support@roadmapos.com if it persists

Status mapping wrong:

Configure → Status Mapping → adjust
Existing initiatives re-sync within 5 minutes

Roadmap OS shows no Jira updates:

Verify Atlassian webhook is active (Atlassian admin → Webhooks)
Verify the Roadmap OS app still has access (your Atlassian admin may have rotated permissions)

Disconnecting

Integrations → Jira → Disconnect

Disconnecting:

Stops the sync
Initiatives stay in Roadmap OS (they don't get deleted)
Jira epics stay in Jira (they don't get deleted)
You can re-connect later; existing initiatives re-link automatically by Jira issue ID

Connecting Jira Cloud