Github for Atlassian - PR merge not updating PR in Jira

[John Philippakos]

So when I open a PR in a branch that has my jira ticket number in the branch name, the PR is visible in my jira ticket..... all builds are also showing. However when I merge the PR, in jira it still shows as OPEN (this has happened with two different tickets, the first a week ago, the second today. This of course is causing my automation (which was working a month ago or so) to fail and not transition my ticket. Both PRs, on both branches, for both tickets are showing merged in github. All other communications between github and jira seem to be working (branches are showing in tickets, PRs are showing, builds are showing, commits are showing).... and all automations attached to those other communications are working just fine..... it is just PR merged that is not working! This seems to have happened around the same time that Github for Jira became Github for Atlassian.... Any ideas?

Thanks in advance!

[Brita Moorus]

Hi, @John Philippakos! 👋

This is a known Jira Cloud issue where merged PRs sometimes remain marked “Open” in the Development panel. Here’s what to do:

1. Go to Jira Settings → Apps → GitHub for Jira → DVCS accounts, then click Backfill to reprocess PR statuses.

2. Edit the PR in GitHub (f.e change the title or add a comment) to trigger a webhook event.

3. Verify in GitHub that your OAuth integration has access to send merge status events.

That should properly update merged PRs in Jira and restore your automation triggers.

Link to KB article: https://support.atlassian.com/jira/kb/github-pr-status-not-updated-in-jira-development-panel 

Let me know how it goes! ✨

[John Philippakos]

I tried backfill and editing the PR with my first of the two PRs, and unfortunately it did not work. As for my OAuth integration, it doesn't specifically mention PRs, but the jira integration has full permissions for everything it is designed to do.

[John Philippakos]

One thing I did notice, this issue coincided with when I added builds to my workflows.... in jira, even though it shows all builds including the succesful ones in the build history, on the ticket itself it still shows failing builds, which when I click on it it goes to the last failing build.... So it seems that if the PR has failing builds, the jira ticket stops syncing once the builds start succeeding.