Jira and Bitbucket extension for VS Code - No more local Git repository detection --> no redirection when remote is an alias of true URL

[FALLAI Denis]

Hi,

Since version 3.0.0, the extension no longer detects local Git repositories cloned from Bitbucket Enterprise (not cloud).
A return to version 2.10.12 solves the problem.

VS Code's native SCM-Git functions work smoothly, as do Git-specific extensions like GitLens or Git Graph.

Extension version: since 3.0.0
VS Code version: 1.74.3
Bitbucket version: Atlassian Bitbucket v7.9.1 (Data Center)

Version 3.0.x:

‌

Downgrade to version 2.10.12:

‌

Local repository:

‌

Remote repository:

‌

[Yakir Gibraltar]

I have the same issue on version 3.0.0 and 3.0.1 , downgrade to 2.10.12 resolve this issue

[Conrad van Straaten]

Same issue here. I keep on getting authentication error messages. Even though I am authenticated. Logging out and back in doesn’t seem to resolve the issue.

‌

[Jeremy Fiel]

same here. i have multiple repos in a single workspace and used to get all PR notifications. Now i’m only able to see two repos, of course the least used repos in my workspace.

[Lu Do]

Same issue for our private Bitbucket server, rollbacked the extension.

[Alex D]

Same.

Can someone from atlassian please look into this issue?

[FALLAI Denis]

Hi,

The origin of the problem has been identified:

• our Enterprise Bitbucket server has changed URL: address and port are different
• the old URL was kept as an alias
• if we clone a Repository using the alias, then the VS Code extension does not work for Pull Request management
• if we clone a Repository using the real address, or if we modify the remote information in a Repository cloned with the alias, then the VS Code extension works for Pull Request management

Conclusion: The VS Code extension does not handle URL redirection requests to access the Enterprise Bitbucket server.

‌