Per-pair page

GitHub + Jira: keep code and tickets in lockstep.

Mirror GitHub PR status into Jira issues, or create GitHub branches from Jira issue keys. The classic dev-tracker pair.

Connect Jira and GitHub See reverse direction

Trigger app

Jira as the trigger

Workflows fire when something happens in Jira.

See all 6 triggers →

Action app

GitHub as the action

Workflows do something in GitHub, instantly.

See all 23 actions →

Both directions

Pick the way that fits your stack.

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

Jira → GitHub

When something happens in Jira, do it in GitHub.

6 Jira triggers wired to 23 GitHub actions. Most-used pairing: Comment Created → Add Labels.

GitHub → Jira

Or fire it the other way around.

1 GitHub triggers wired to 17 Jira actions downstream.

New GitHub Event

See GitHub → Jira →

Popular pairings

Common Jira → GitHub workflows.

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

Showing 9 of 138 combinations

When comment created in Jira, add labels in GitHub.

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 comment in GitHub.

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

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 pull request in GitHub.

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 labels in GitHub.

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 comment in GitHub.

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

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 pull request in GitHub.

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 labels in GitHub.

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 GitHub in five steps.

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

1
Connect
Authorize Jira and GitHub
Open Tiny Command, authorize Jira and GitHub 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 GitHub action
Drop the GitHub → Add Labels action below it. Map fields from the Jira payload into the GitHub inputs.
github.add-labels-to-issue
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 + GitHub.

Doesn't Jira already have GitHub integration?

Yes — Jira's native GitHub integration handles basic linking. The pair on Tiny Command extends it with custom workflows: AI-summarize PRs into Jira comments, auto-transition issues, propagate labels, etc.

How do I auto-transition a Jira issue when a GitHub PR is merged?

GitHub PR Merged trigger → parse Jira key from PR title (e.g., "PROJ-123") → Jira Transition Issue to "Done" using Get Transitions to find the right transition ID first.

Can I create GitHub branches from Jira issue keys?

Yes. Jira Issue Updated to "In Progress" → GitHub Create Branch named "{issue_key}-{slugified_title}". Standardizes naming and removes manual branch-naming friction.

How do I summarize a GitHub PR as a Jira comment?

GitHub PR Merged → fetch PR diff → AI summarize → Jira Add Comment on the linked issue with the summary. Non-engineer stakeholders get a digest without reading code.

Can I auto-assign GitHub PR reviewers based on Jira fields?

Yes. On PR Opened, look up the linked Jira issue by branch name → read the "Component" or "Tech Area" custom field → request review from the matching code-owner team via GitHub API.

How do I keep Jira sprint board accurate based on GitHub state?

GitHub is the source-of-truth for engineering state (open, in review, merged). Jira mirrors via the relevant triggers. Engineers never have to manually update Jira; the sprint board reflects code reality.

Other apps that pair well with Jira.

Spreadsheets & Databases

Wire Jira to GitHub in 2 minutes.

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

Try for free Request a demo

GitHub + Jira: keep code and tickets in lockstep.

Pick the way that fits your stack.

When something happens in Jira, do it in GitHub.

Or fire it the other way around.

Common Jira → GitHub workflows.

Connect Jira and GitHub in five steps.

Questions about Jira + GitHub.

Other apps that pair well with Jira.

Wire Jira to GitHub in 2 minutes.

Be the first to know what's next.