I have the same problem, but I'm using the Azure DevOps repository. The pull request is closed, but the status is still OPEN in Jira. Are there any solutions?

Same issue

Facing this issue, any resolution yet?

This issue is not fixed. There should be a way to re-trigger an update. Adding a comment doesn't work for me.

Thanks a lot CJ, 

our team tested the workaround and it’s working

Just note that the webhook payload request failed, and need to be "redeliver".

Data Center v8.13.

The workaround for our teams is this.
Go to the PR on Github:

• ensure the name convention is correct for linking back to Jira  ← more common problem than one would think
• add a new comment to the PR (not Jira)

For us, this sends new data to Jira and the 'stuck' statuses are then corrected to reflect the actual status of the PR.

Same problem occurred with  Jira v8.5.3.

Why is this issue closed?

What is the workaround?

Same Problems with Jira 8.13.3 Server...

We have had this problem since Jira 6 and still with Jira 8

Mysterious to me met with that on 8.5.4 release

Our Team has the issue too with Jira Server Version 8.11.1.
With the mentioned fix (deletion of entries and Refresh account on DVCS page) the status of the pull requests are updated to merged. It would be nice if some one can look into it, because the workflow trigger don't work as expected because of the wrong PR status. 

We have the issue with Github-Integration (DVCS-Account).

This is a long-fixed issue but our team is seeing the problem again right now (with Jira v7.13.1) - we have a couple pull requests stuck in Open state even though in GitHub they show as merged and the associated branch has been deleted. We tried commenting on the PR to refresh it, but it's still showing as open.

Hi, we still has this issue. Any idea?

DVCS Connector 2.0.4 for versions 6.2.x of JIRA for Download is on Marketplace now. To get this fix, you could upgrade the plugin from the Manage Add-On page within JIRA.

The issue has been fixed but data already synchronized will not be automatically fixed.
To fix the synchronized data you can do the one of the following:

1. Particular pull request will be updated if some change on the pull request is done, e.g. the comment is added
2. To force all the pull requests to synchronize again, delete the GitHub events for the repository
   delete from "AO_E8B6CC_GIT_HUB_EVENT" where "REPOSITORY_ID" = 1234;, where 1234 is the id of the repository to be resynchronized. This will not delete any pull request data, it will only go through all the GitHub events and update the existing pull requests.