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 Jira and Linear See reverse direction

Trigger app

Jira as the trigger

Workflows fire when something happens in Jira.

See all 6 triggers →

Action app

Linear as the action

Workflows do something in Linear, instantly.

Both directions

Pick the way that fits your stack.

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

Jira → Linear

When something happens in Jira, do it in Linear.

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

Linear → Jira

Or fire it the other way around.

6 Linear triggers wired to 17 Jira actions downstream.

See Linear → Jira →

Popular pairings

Common Jira → Linear workflows.

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

Showing 9 of 48 combinations

When comment created in Jira, add comment in Linear.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, create issue in Linear.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, get issue in Linear.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When comment created in Jira, list issues in Linear.

Fires when a comment is added to a Jira issue. Used to mirror engineering discussion to Slack, feed AI summaries, or notify external requesters.

When new issue in Jira, add comment in Linear.

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

When new issue in Jira, create issue in Linear.

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

When new issue in Jira, get issue in Linear.

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

When new issue in Jira, list issues in Linear.

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

When issue deleted in Jira, add comment in Linear.

Fires when an issue is deleted in Jira. Useful for audit/compliance logs and for tearing down related records in other systems.

How it works

Connect Jira and Linear in five steps.

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

1
Connect
Authorize Jira and Linear
Open Tiny Command, authorize Jira and Linear once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Jira trigger
Drop the Jira → Comment Created trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/jira.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 Linear action
Drop the Linear → Add Comment action below it. Map fields from the Jira payload into the Linear inputs.
linear.create-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 Jira + Linear.

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 Jira.

Spreadsheets & Databases

Wire Jira to Linear 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 Jira, do it in Linear.

Or fire it the other way around.

Common Jira → Linear workflows.

Connect Jira and Linear in five steps.

Questions about Jira + Linear.

Other apps that pair well with Jira.

Wire Jira to Linear in 2 minutes.

Be the first to know what's next.