[BUG] Existing pull requests and branches links are broken after 8.21.0 update

[PopUp House]

Hello,

After updating Jira Server from 8.19.1 to 8.21.0 and Bitbucket Server from 7.15.0 to 7.19.0, I have issues with existing branches and pull requests

Steps to reproduce :

When I click on a branch or pr link, it shows an error "You don't have access to view all related pull requests. Please contact your administrator." or "You don't have access to view all related branches. Please contact your administrator."

API request from browser console :

GET https://<myjira>/rest/dev-status/1.0/issue/detail?issueId=<myid>&applicationType=stash&dataType=pullrequest

{
  "errors": [],
  "detail": [
    {
      "branches": [],
      "pullRequests": [],
      "repositories": [],
      "_instance": {
        "applicationLinkId": "<myappid>",
        "baseUrl": "https://<mybitbucket>",
        "primary": true,
        "singleInstance": false,
        "name": "PopupBucket",
        "typeName": "Bitbucket Server",
        "id": "<myappid>",
         type": "stash"
       }
     }
   ]
}

Actions :

I performed a full reindex, deleted the bitbucket link (both ways), tried Oauth and Oauth with impersonation methods but it didn't fix it.

Workaround :

New branches and PRs are not impacted and the workaround to fix existing PRs is to close then reopen them. It also fixes the branch link at the same time.

{
  "errors": [],
  "detail": [
    {
      "branches": [
        {
          "name": "ESKP-77-correction-des-btl-de-top-plate",
          "url":
... 

[m1m1n0 · Accepted solution]

It's this bug: https://jira.atlassian.com/browse/BSERV-13097

[Brian Keefe]

Thank you.

[PopUp House]

Awesome, thanks @m1m1n0 !
The workaround provided in the issue works for me :

Via Postman :

POST https://{your_bitbucket_instance}/rest/jira-dev/1.0/projects/{your_project_key}/repos/{your_repo}/reindex

Authorization :
Type : Basic Auth
Username + Password : same as bitbucket

Additional header :
X-Atlassian-Token: no-check

[Don Masten]

Seeing this with JIRA 8.17.1 and Bitbucket 7.19.1

[Bas]

Same here, upgraded from Bitbucket 7.17.1 to 7.19.1. 
Jira still at 8.20.1

[Agilent Technologies Inc.]

Same issue with jira v8.20.1 and upgrade to bitbucket 7.19.0 from 7.17.1

Any way to apply a global fix?

Also apply to closed PR

Thanks

[Alexandra King]

Is there a feasible fix for this yet? Same issue after upgrading to BB 7.19.1.

[Andreas Emer]

I can confirm this issue, we have the same problem after updating to the most current version of Jira 8.21.0 and Bitbucket 7.19.0.

[Jonathan Hogarth]

We upgraded to BitBucket v7.19.1 and Jira v 8.20.3 last night and noticed the exact same behavior.  Our stack is Atlassian Data Center tier of products.

[Benedikt S.]

We have the same problem with Jira 8.19.1 and Bitbucket Server from 7.19.1, after we upgraded from Bitbucket Server 7.17.1.

[m1m1n0]

We have the same problem after upgrade to Bitbucket v7.19.0 while Jira is at v8.20.1