In Bitbucket Server 4.3,
BSERV-7360 was fixed and the UI was updated to wait the configured server-side merge timeout when merging a pull request and when checking if it could be merged. It appears the "canMerge" portion of that fix was almost immediately regressed, in 4.4.0. As a result, while the UI will still wait the configured merge timeout when merging a pull request, viewing a pull request can still show a "Server unreachable" popup while checking mergeability.
Because the mergeability check result is cached, so long as the pull request doesn't change, refreshing the screen after a timeout will (generally) show the correct mergeability state very quickly, since it doesn't need to perform a new merge.
- is a regression of
BSERV-7360 Front end for pull request merges should wait as long as server does for process to complete
- is related to
BSERV-10235 The UI only waits 1 minute for ref sync merges
- mentioned in