Try or ByeTry or Bye

Linear Issue Not Closing When PR Is Merged

Workaround available Web, macOS, Windows Updated October 21, 2026

Quick answer

Usually caused by a non-closing magic word ('ref', 'part of'), another linked PR still open, or the team's merge automation set to no action. Use 'Fixes ENG-123' and check Settings > Team > Workflows & automations.

Most likely fix: Use a closing magic word.

Symptoms

The PR is merged on GitHub but the Linear issue stays In Progress or In Review instead of moving to Done.

Why it happens

  • Non-closing magic word used (ref, refs, part of, contributes to)
  • Several PRs linked and one is still open
  • Merge automation set to 'no action' or pointing at a renamed/deleted status
  • Branch-specific rule overrides the default for the target branch
  • Squash merge from a branch whose earlier PRs were linked

How to fix it

Try these in order — the most common fix is first.

  1. 1. Use a closing magic word

    1. Edit the PR description
    2. Use close/fix/resolve/complete/implement before the ID, e.g. 'Fixes ENG-123'

  2. 2. Check every linked PR

    1. Open the issue and review all PR attachments
    2. Close or remove PRs that will never merge (three dots on the attachment > Remove)

  3. 3. Review team automations

    1. Go to Settings > Team > Workflows & automations > Pull request and commit automations
    2. Make sure 'merged' maps to an existing Done status
    3. Check branch-specific rules for main/staging

  4. 4. Relink after squash merges

    1. Add the issue IDs again to the final PR title or description

This guide also covers

  • linear issue not moving to done
  • linear pr merged status not updating
  • linear github automation not working

Still not working?

If Linear keeps failing, you're not alone. See every Linear problem users report or the alternatives people switch to.

Other Linear errors