Pull Request status still remain Open

[Marco Oliverio]

Hi to all, I'm Marco from Italy

I've a question about pull request status in Jira Software
Example:

I have created  a pull request and correctly see the Pull request in Develop panel of the Related issue (the pull request name contain the issue KEY), but If I merge that pull request
and in bit bucket I see the pr as Merged, in Jira still remain as "opened". There is only 1 pull request.
If I click in jira for viewing all pull request The system show me the pull request is MERGED but in develop panel remains open.
This is giving me Crazy :D
What am I doing wrong?
Thanks for the replies
Marco

[DNIssueCollector]

I'm using Jira Cloud and found that I can run a full sync to force Jira to re-read all PRs on the GitHub side. This hasn't resolved the issue, as we are still finding PRs that aren't updating, but it does seem to retroactively address this.

Jira Settings > Apps > Manage Apps > expand GitHub > Get Started > dropdown Full > Submit

It's a lengthy operation so I tend to run it in off hours. Hopefully multiple syncs doesn't hurt me in the long run. . . 

[karenann]

I am also experiencing the issue described in the original problem.

Let me show two images to visually describe the problem.

In this first attached image, you can see that the "Development" column in the Release shows "UNDER REVIEW" and the details show that pull request "8.x-2.7 RC 1" is listed as open.

In this second attached image, you can see that this pull request is, in fact, merged. However, I cannot get Jira to recognize that it is merged.

[paula.catharina]

I am having the same problem here, it doesn't happen often, but sometimes it does and it drives me crazy.

Did you guys find some solution? Belto posted this bug below: https://jira.atlassian.com/browse/JSWCLOUD-17240 but it is not what is happening, because my pull requests that are not updated accordingly have commits in it recognized by the Jira development field.

[Mandia]

I have the same issue. Any solution ?

[cpedraza]

I had the same issue. I solved it by changing the name of the PR in github (post merge) to add the Jira ticket name ("WWW-2063" in this example). That seemed to trigger an update and it appears as on Jira as merged now (instead of open).

[cpedraza]

I had the same issue but on Github.

I solved it by changing the name of the PR in github (post merge) to add the Jira ticket name ("WWW-2063" in this example). That seemed to trigger an update and it appears as on Jira as merged now (instead of open). It may work if you update the title with something else. I just figured adding the ticket name would help since it's what links PRs to issues.

[Matthew J_ Becker]

I just had this happen with Jira/Bitbicket Cloud. I un- and re-approved the merged Pull Request, and the Jira issue picked up the change then.

[valdes21]

Same problem here. I'm using Jira Server 8.5.1 with BItbucket Cloud. When the pull request on Bitbucket becomes "Merged" Jira doesn't get it. I have to switch to administration menu and enforce the sync of the particular Bitbucket repository with Jira. The Jira issue get's the right state then. It's really annoying, cause it happens with every pull request. Does anyone have a solution?

[valdes21]

I found the solution in my case. The Bitbucket webhook for merged and declined pull requests was not set. See picture attached. After I activated both checkboxes the problem was solved.

[valdes21]

I found the solution in my case. The Bitbucket webhook for merged and declined pull requests was not set. See picture attached. After I activated both checkboxes the problem was solved.

[valdes21]

Same problem here. I'm using Jira Server 8.5.1 with BItbucket Cloud. When the pull request on Bitbucket becomes "Merged" Jira doesn't get it. I have to switch to administration menu and enforce the sync of the particular Bitbucket repository with Jira. The Jira issue get's the right state then. It's really annoying, cause it happens with every pull request. Does anyone have a solution?

[Zachi Meyer]

Hi everyone,

I have JIRA server and I have this problem too (I don't have web hook).

How did you solve the problem?

[Inaki Berra]

Figured something out. If you want the status to show "Merged" you need to delete the branch of the PR. In that way, the status is updated to Merged.

Also, if you want the PR to appear open, there should be at least one reviewer.

[karenann]

FWIW. The branch of the merged pull request is long deleted and still shows, in mine, as Open.

[Timothy]

Merging a pull request in Bitbucket does not automatically change the status of the Jira issue unless you have configured it to do so with the Triggers in Issues workflow.

• https://confluence.atlassian.com/adminjiraserver071/configuring-workflow-triggers-802592811.html

[Marco Oliverio]

Hi Timothy thanks for the reply
Mi problem isn't the issue status but the pull request status, which remain "open", meanwhile I have a merged request pull inside (is only one)
Marco

[fdumas3]

I'm also experiencing this issue but with the GitHub integration.   The pull request status shows as "open" in JIRA even though it's merged in Github

[Belto]

https://jira.atlassian.com/browse/JSWCLOUD-17240

[Meigy Tsai]

@Belto Actually, that ticket JSWCLOUD-17240 doesn't capture the issue with GitHub. At least in our instance, we do have commits, and there is even a branch.. which has been merged.. and then deleted.

[Simon Jazbar]

@Meigy Tsai you managed to fix this issue? Do you have a workaround?

[cpedraza]

@Simon Jazbar @Meigy Tsai 
I had the same issue. I solved it by changing the name of the PR in github (post merge) to add the Jira ticket name ("WWW-2063" in this example). That seemed to trigger an update and it appears as on Jira as merged now (instead of open).

[Surendra Singh Kushwaha]

@Meigy Tsai its only happen when jira fetch PR detail when it was Open, after code merge jira not fetch detail, you can check datetime in jira for same PR and merge datetime in merged branch.