Hello All,
Atlassian Lab VsCode extension manages to login successfully.
Able to see the list of existing PRs. But it failed with an below-mentioned error when I tried to unfold the Pull request.
"Error: fetching pull request details failed"
Can anyone suggest how to fix it or which combination of versions of vscode and extension to be used?
Details:
VS Code Version: 1.91.1
Jira and Bitbucket (Atlassian Labs): 3.0.10
Regards,
Hi and welcome to the community!
Could you please let us know if you're using Bitbucket Cloud, Server, or Data Center? In case it is Server or Data Center, what version are you using?
Your question has the tag 'bitbucket-cloud', but your Bitbucket Cloud account doesn't have access to any repositories with pull requests.
If you are unsure, the URL of a Bitbucket Cloud repository on your browser starts with https://bitbucket.org/, while Bitbucket Server and Data Center have a different custom URL.
Does this issue occur with all PRs or only with a specific one?
Kind regards,
Theodora
Using Bitbucket Data Center v8.19.2
I'm getting this same issue with all of my PRs. If I right click the PR and 'View in Browser' I'm taken straight to the PR in my browser. I'm also able to change with PRs I want to see. The PR list updates with the PR type I request. For Example, Clicking on 'Show declined pull requests' updates the list with the correct list of declined PRs. Clicking 'Show all open pull requests' changes the list to the correct PRs that are still open.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Exact same problem here.
VSCode 1.86.1
Bitbucket Data Center 8.19.6
Plugin 3.0.9
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1
I have the same issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
+1 more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have same issue, but I can see the problem. Bitbucket DC deprecated the /tasks endpoint and we should hit the /blocker-comment endpoint. Seems plugin has not been updated to reflect this change. I guess due to backward compatibility
Can manually update the extension.js and replace /tasks with /blocker-comments and where /tasks/count replace with /blocker-comment?count=true
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.