The world's largest code hosting platform with Git version control, collaboration features, CI/CD, and project management.
Full ReviewAtlassian's project management tool built for agile software development teams with sprint planning, boards, and roadmaps.
Full ReviewThe GitHub-Jira integration is one of the most widely used dev tool connections in the industry, linking source code management with issue tracking. When developers reference Jira issue keys in commit messages, branch names, or pull request titles, the integration automatically updates the Jira issue with development status. This gives product managers and engineering leads real-time visibility into which issues have code in progress, in review, or deployed.
Atlassian provides a native GitHub for Jira integration available on the Atlassian Marketplace, free for all Jira plans. The integration connects via a GitHub App that sends webhook events to Jira Cloud. It supports branch tracking, commit references, pull request status, deployment information, and build status — essentially the full software development lifecycle visible within Jira issues.
This integration works with both Jira Cloud and GitHub.com. For Jira Data Center (self-hosted), Atlassian offers a separate marketplace app. The native integration has become increasingly sophisticated, supporting Jira's development panel that shows a complete timeline of code activity per issue without leaving Jira.
| Method | Difficulty | Features |
|---|---|---|
| GitHub for Jira (Atlassian Marketplace) | Easy | Branch, commit, PR, build, and deployment tracking on Jira issues |
| Zapier | Easy | Triggers: New PR, Issue Created. Actions: Create Issue, Transition Issue, Add Comment |
| API | Advanced | GitHub REST API + Jira Cloud REST API (/rest/api/3/) for custom workflows |
In Jira Cloud, go to Apps > Explore more apps (or visit marketplace.atlassian.com). Search for "GitHub for Jira" and install the official app by Atlassian. You need Jira administrator permissions. The app is free and included with all Jira plans.
After installation, go to Apps > Manage apps > GitHub for Jira > Get started. Click Connect GitHub organization and sign in to GitHub. Install the Jira GitHub App on your GitHub organization, selecting which repositories to grant access to. You need GitHub organization owner or admin permissions.
The integration offers to backfill existing commits, branches, and pull requests that reference Jira issue keys. This scans your Git history for patterns like "PROJ-123" in commit messages and branch names, linking them to Jira issues retroactively. For large repositories, backfilling can take several hours — the process runs in the background.
Enable Jira Smart Commits to allow developers to transition issues and log time from commit messages. The syntax is: PROJ-123 #done #time 2h Fixed the authentication bug. In Jira, go to Settings > Products > DVCS accounts and verify Smart Commits are enabled for the connected GitHub account.
Create Jira automation rules that respond to development events. Go to Project Settings > Automation > Create rule. Common rules include: "When a branch is created → transition issue to In Progress" and "When a pull request is merged → transition issue to Done." These rules use the development triggers provided by the GitHub integration.
| Data Type | From GitHub | To Jira | Direction |
|---|---|---|---|
| Branches | Branch names containing issue keys | Development panel on issues | GitHub to Jira |
| Commits | Commits with issue keys in messages | Development panel with commit details | GitHub to Jira |
| Pull requests | PR title/description with issue keys | PR status (open, merged, declined) | GitHub to Jira |
| Build status | GitHub Actions workflow results | Build indicator on issues | GitHub to Jira |
| Deployments | GitHub Deployments API events | Deployment tracking on issues | GitHub to Jira |
A team uses Jira for sprint planning with a board showing To Do, In Progress, In Review, and Done columns. When a developer creates a branch named "feature/PROJ-123-user-auth," the Jira issue PROJ-123 automatically moves to In Progress. When they open a PR, it moves to In Review. When the PR merges, it moves to Done. The sprint board stays current without anyone manually dragging cards.
At release time, the engineering manager filters Jira issues by Fix Version and sees every linked PR and commit. Since each Jira issue references the specific code changes, generating release notes is a matter of listing the completed issues with their descriptions. The development panel shows exactly which commits went into the release, providing an audit trail from requirement to deployed code.
The integration matches Jira issue keys (e.g., PROJ-123) in commit messages. Verify the project key exists in your Jira instance and that the issue number is valid. The key must be an exact match — "proj-123" (lowercase) may not match depending on configuration. Check that the repository has the Jira GitHub App installed by going to GitHub > Repository Settings > Integrations.
If the development panel shows no data, first check that the GitHub for Jira app is properly connected in Jira > Apps > Manage apps. Verify the GitHub organization has the Jira app installed. If the integration was recently set up, the backfill process may still be running — check the integration status page. For new commits, verify webhooks are being delivered by checking GitHub > Organization Settings > Webhooks for recent deliveries.
The integration is one-directional — GitHub data flows to Jira, but you cannot create GitHub issues or PRs from Jira natively. Jira issue key matching requires the key to appear in the branch name, commit message, or PR title/description — code comments referencing issue keys are not detected. The backfill process for large repositories with thousands of commits can time out or miss references in very old commits. GitHub Enterprise Server (self-hosted) requires a different integration app from the Atlassian Marketplace. Smart Commits only support a limited set of Jira actions: transition, time tracking, and comments — custom field updates via commit messages are not supported.
These platforms can help you connect GitHub and Jira without writing code:
