Per-pair page

Jira + Linear: bridge two engineering trackers.

Sync Jira issues with Linear issues during migrations, in M&A scenarios, or when different teams in the org use different trackers but work overlaps.

Connect Linear and Jira See reverse direction

Trigger app

Linear as the trigger

Workflows fire when something happens in Linear.

See all 6 triggers →

Action app

Jira as the action

Workflows do something in Jira, instantly.

See all 17 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Linear → Jira

When something happens in Linear, do it in Jira.

6 Linear triggers wired to 17 Jira actions. Most-used pairing: Comment Created → Add Comment.

Jira → Linear

Or fire it the other way around.

6 Jira triggers wired to 8 Linear actions downstream.

See Jira → Linear →

Popular pairings

Common Linear → Jira workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 102 combinations

When comment created in Linear, add comment in Jira.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When comment created in Linear, add watcher in Jira.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When comment created in Linear, assign issue in Jira.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When comment created in Linear, create issue in Jira.

Fires when a comment is added to a Linear issue. Use to mirror engineering discussion to Slack or to feed AI summaries into a status doc.

When new cycle in Linear, add comment in Jira.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new cycle in Linear, add watcher in Jira.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new cycle in Linear, assign issue in Jira.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new cycle in Linear, create issue in Jira.

Fires when a new cycle (sprint) is created in Linear. Use to kick off stand-up bots or to seed a cycle-kickoff doc.

When new issue in Linear, add comment in Jira.

Fires when a new issue is created in Linear. The standard inbound hook for routing, enrichment, and SLA-aware notifications.

How it works

Connect Linear and Jira in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Linear and Jira
Open Tiny Command, authorize Linear and Jira once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Linear trigger
Drop the Linear → Comment Created trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/linear.trigger-comment-created
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Jira action
Drop the Jira → Add Comment action below it. Map fields from the Linear payload into the Jira inputs.
jira.add-comment
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Linear + Jira.

When does Jira + Linear sync make sense?

Migrations (gradual cutover), M&A (acquired team uses different tracker), or different teams that picked different tools. The pair keeps work visible in both while you decide on standardization.

How do I avoid duplicate issues?

Store the foreign ID on each side — Jira custom field "Linear ID", Linear comment or label with Jira key. Upsert by looking up the foreign ID before deciding create vs. update.

Should I sync status both ways?

Pick one side as source-of-truth for status (whichever team owns the work). Sync status one-way from there. Bidirectional status sync ping-pongs and breaks the trackers' workflows.

How do I map Jira projects to Linear teams?

Maintain (jira_project_key → linear_team_id) lookup. The workflow consults at Create Issue time. Updates use the lookup to find the matching destination.

Can I sync Jira custom fields to Linear?

Linear has limited custom fields. For structured fields (priority, estimate, labels), direct mapping works. For free-form custom data, stuff it into Linear description as a structured block.

How do I sync comments between the two?

One direction only. Pick the side where engineers actually comment (Linear usually) and mirror to the other. Bidirectional comment sync causes duplication and threading confusion.

Other apps that pair well with Linear.

Linear + Gmail

Linear + Slack

Communication

Linear + Google Sheets

Spreadsheets & Databases

Wire Linear to Jira in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for free Request a demo

Jira + Linear: bridge two engineering trackers.

Pick the way that fits your stack.

When something happens in Linear, do it in Jira.

Or fire it the other way around.

Common Linear → Jira workflows.

Connect Linear and Jira in five steps.

Questions about Linear + Jira.

Other apps that pair well with Linear.

Wire Linear to Jira in 2 minutes.

Be the first to know what's next.