Automatically transition Jira issues as GitHub pull requests move through their lifecycle. No more chasing developers to update ticket status.
See how it worksSprint Sync listens to GitHub webhook events and transitions the linked Jira issue in real time — so your board always reflects what's actually happening in code.
GitHub webhooks trigger Jira transitions within seconds of a PR event. Your sprint board reflects reality, not yesterday's standup.
Sprint Sync reads Jira keys from PR titles, branch names, and commit messages. Works with or without strict naming conventions.
Map any GitHub event to any Jira transition. Works with custom workflows — not just Jira's defaults. Target specific branches for each rule.
Optionally block a transition if conditions aren't met — e.g. only mark Done on merge to main, not feature branches.
Automatically adds a comment and smart link to the Jira issue whenever a PR is opened or merged, so the connection is always visible.
Connect multiple GitHub repos to multiple Jira projects. Define different transition rules per repo or inherit org-level defaults.
Sprint Sync ships with sensible defaults. Every mapping is overridable — adjust the target statuses to match your team's workflow.
| GitHub event | Condition | Jira transition |
|---|---|---|
| Branch created | Branch name contains a Jira key | → In Progress |
| Pull request opened | PR title or branch contains a Jira key | → In Review |
| Pull request review submitted | Review state is approved |
→ Ready for QA |
| Pull request closed | Merged into main or master |
→ Done |
| Pull request closed | Closed without merging | → To Do (reverts) |
| Pull request reopened | Any | → In Progress |
Deploy to your Jira site via the Forge CLI. Sprint Sync installs as a Jira app — no separate server or webhook infrastructure needed.
Add a GitHub webhook pointing to Sprint Sync's endpoint. Select which repos to track from the Jira settings page.
Use the default mappings or customise them to match your Jira workflow. Set per-branch rules if you need different behaviour on different targets.
From this point on, Jira reflects GitHub. Developers work in their IDE; the sprint board stays current automatically.
We configure Sprint Sync for your Jira workflows and GitHub repos. Get in touch to discuss your setup.
Contact us