GitHub pull request status is not updated after merging. Pul request status should be changed from OPEN to MERGED, but it remains OPEN.

            [JSWSERVER-14247] GitHub pull request status is not updated

            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?

            Adrian Rutkowski added a comment - 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

            Kamnev Yuriy added a comment - Same issue

            piroska.barjak added a comment - - edited

            I am facing this issue now. Closed a PR, but Jira still shows it open. There are two PRs connected to the issue.

             

            Commenting on it did not solve it.

            piroska.barjak added a comment - - edited I am facing this issue now. Closed a PR, but Jira still shows it open. There are two PRs connected to the issue.   Commenting on it did not solve it.

            Facing this issue, any resolution yet?

             

            RASHMI METRI added a comment - 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.

            Viktor Nikolenko added a comment - 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".

             

            Valerie Denis added a comment - 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".  

            CJ Edwards added a comment -

            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.

            CJ Edwards added a comment - 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?

            Valerie Denis added a comment - 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...

            Timo Keilbach added a comment - Same Problems with Jira 8.13.3 Server...

            CJ Edwards added a comment -

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

            CJ Edwards added a comment - We have had this problem since Jira 6 and still with Jira 8

              Unassigned Unassigned
              mstencel MiroslavA
              Affected customers:
              0 This affects my team
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: