[Bitbucket Server] PR create / tracking no longer works since Bitbucket DataCenter / Enterprise server version 8.x.x.x upgrade

[FALLAI-Denis]

Describe the bug

Since the upgrade to version 8.x.x.x of Bitbucket DataCenter / Enterprise server, the creation of a PR works, but afterwards an error is displayed which prohibits the tracking of this PR, and prohibits the merge action on this PR from VS Code.

Everything worked in version 7.x.x.x of Bitbucket DataCenter / Enterprise Server.

According to the information displayed, the extension uses an API that was deprecated in version 7.x.x.x and which was removed in version 8.x.x.x.

See the various open tickets on the Atlassian site, including issue 756 Error on Pull Request creation and browsing

To Reproduce

Steps to reproduce the behavior:

1. Go to Jira and Bitbucket activity
2. Create a new PR
3. See error after creating PR

Expected behavior

No error....

Screenshots

Environment and Version (please complete the following information):

• Atlassian Plugin Version (x.x.x)
• Visual Studio Code Version: all
• Is this a local or cloud environment? local
• If Cloud, Browser (chrome, safari)
• If Local, OS (macOS, windows, linux): Windows 10 22H2

Additional context

See;

• Error on Pull Request creation and browsing
• Error fetching pull request details from Bitbucket
• VSCODE-1422 - fix task fetching and editing

[ebresie]

Not sure if this is the same problem or a slightly different issue (if it is I can raise a separate issue).

As of 3.4.0 in the "BITBUCKET PULL REQUESTS" area, for a given "repo/project", it lists the "PR" identifier, but below this, it shows "Error: fetching pull request details" and does not open any corresponding window.

After looking this may actually be already covered by #25

Not sure if they are possibly related though. In other issue, it had been changes in APIs (on the ticket relating to JIRA). Not sure if there is a similar "API" change associated with BitBucket side of things.

[yakirgb]

Same issue:

[schlappette]

Relevant comment in #25

[bwieger-atlassian-com]

Thanks all!

Will solve as part of AXON-113

[bwieger-atlassian-com]

This should be fixed in 3.4.5. It will be released later today or tomorrow.

[bwieger-atlassian-com]

3.4.5 is released!