Skip to content
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.

Trigger app
GitHub as the trigger

Workflows fire when something happens in GitHub.

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.

GitHubJira

When something happens in GitHub, do it in Jira.

1 GitHub triggers wired to 17 Jira actions. Most-used pairing: New GitHub EventAdd Comment.

JiraGitHub

Or fire it the other way around.

6 Jira triggers wired to 23 GitHub actions downstream.

See JiraGitHub
Popular pairings

Common GitHub → Jira workflows.

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

Showing 4 of 17 combinations
How it works

Connect GitHub and Jira in five steps.

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

  1. 1
    Connect
    Authorize GitHub and Jira

    Open Tiny Command, authorize GitHub and Jira once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a GitHub trigger

    Drop the GitHub → New GitHub Event trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/github.trigger-event
  3. 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. 4
    Action
    Add the Jira action

    Drop the Jira → Add Comment action below it. Map fields from the GitHub payload into the Jira inputs.

    jira.add-comment
  5. 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 GitHub + Jira.

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

Other apps that pair well with GitHub.


Wire GitHub to Jira in 2 minutes.

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