Guide
Move Jira tickets automatically when pull requests merge
The code already knows what's happening: a branch was created, a pull request opened, a merge landed. The ticket should know too. Here's how to make Jira and Linear tickets move on their own as the code moves, without surprising anyone.
Updated October 10, 2026 · 5 min read · By the Align team
The moves that matter
| When this happens in GitHub | The ticket moves to |
|---|---|
| A branch is created or the first commit is pushed | In Progress |
| A pull request is opened | In Review |
| The pull request is merged | Done |
| Changes are requested on the PR | A note on the ticket |
How the commit finds its ticket
- Put the ticket key in the branch name: eng-231-onboarding-flag. This is the most reliable.
- Or in the pull request title or a commit message: "ENG-231 Add the flag column".
- Without a key, a good tool matches by what the PR describes against your open tickets, and asks before creating a new one.
Jira's built-in automation vs a dedicated tool
Jira Automation with the GitHub for Jira app can transition issues on events, but each project needs its own rules, rules break when workflows change, and they don't cover Linear. Workflows with many steps (To Do → In Progress → In Review → Done) also need a rule per hop.
A dedicated tool reads the workflow and walks the ticket there, fills required fields such as a resolution on Done, and tells you when a move isn't allowed instead of silently failing.
Keep a person in the loop
Automatic moves are great until one is wrong. Start with approve-by-default: each move appears as a one-click card. Once the team trusts it, switch on auto-move for your own tickets and keep an undo.
How Align does this for you
Align watches GitHub through your connected account or the Align GitHub App, and an optional git hook catches each commit the moment you make it. Every move shows as a card in your Plans Inbox ("ENG-231 → In Review?"), or happens on its own if you turn on auto-move for your own tickets. The move syncs to Jira or Linear, walking multi-step workflows and filling the resolution Jira asks for. Each move leaves a short comment linking back to the PR.
Frequently asked questions
Do I need the ticket key in the branch name?
It's the most reliable way, but not required. Without a key, Align matches the PR to the open ticket it describes and asks before creating a new ticket.
Will it move tickets without asking?
Only if you turn on auto-move for your own tickets. By default every move waits for one click, and every automatic move can be undone.