Issue Summary

The PULL_REQUEST_REVIEW_MODE feature flag was removed with the below Stash Pull Request from Bitbucket v.7.x onwards. But the file was missed to be removed from v7.6.x.

• fb672d42345

Therefore in version v.7.6.x, when opening the Pull Request screen it tries to load the non-existent page and throws 404 error in the logs. Although there is no impact to the application, Customers are concerned about high volume of 404 errors in the logs that this issue causes.

/rest/features/latest/user?featureKey=pull.request.review.mode

The Solution is to implement the changes similar to fb672d42345 in the next Bitbucket 7.6.x bug release.
 

Steps to Reproduce

1. Open a Pull Request Screen in the Bitbucket v7.6.x

Expected Results

The application should stay on the below URL and not throw any 404 errors.

<BITBUCKET-BASE-URL>/projects/<PRJ_SLUG>/repos/<REPO_SLUG>/pull-requests/<PR_NUMBER>/overview

Actual Results

The application is trying to load the below URL and throwing 404 error.

/rest/features/latest/user?featureKey=pull.request.review.mode

The below is the sample log.

atlassian-bitbucket-access.log:
XX.XX.XX.XX,XX.XX.XX.XX | https | o*XYC5YFx806x25920719x34 | 18263460 | 2021-12-29 13:26:52,075 | "GET /rest/features/latest/user HTTP/1.1" | "<BITBUCKET-BASE-URL>/projects/<PRJ_SLUG>/repos/<REPO_SLUG>/pull-requests/<PR_NUMBER>/overview" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.110 Safari/537.36" | 404 | 0 | 0 | - | 1 | 1nl8bjw | 

Workaround

Upgrade to Bitbucket v7.7.0 or higher.