VSCode 1.76: Start Work displays "no branches found" in source branch

[Former user]

VS Code: 1.76.0
Jira Extension: atlassian.atlascode 3.0.2
Windows 10

What i see:

When using Start Work ( with WSL2 or Remote SSH or Windows Native ) in the Set up git branch section, the Jira extension find the repository but Source Branch displays no branches found

Same behavior with any repo and any issue.

What i expect:

Source Branch displays the branches of the selected repository.

Additional info:

The rollback to VS Code 1.75.1 fixes the issue.

I’ve tried with login/password or personal token, same behaviour.

‌

[Todd Freeman]

I am experiencing the same issue, and I am on the same version of VS Code.

[Yakir Gibraltar]

Facing same issue , any updates ?

[Ben Gardiner]

yep, same facing the same issue!

[Dominic Saladin]

Yep, same issue here

[Dimitar Dimitrov]

Still facing the same

[Ricardo Gallardo]

I’ve got the same issue, very aggravating.

[Chin Lim]

Yep, same issue

[David Lopez]

I have the same issue. And, I cannot create PRs, can’t find branches

‌

[Spyros Psarras]

Same here.
I have enabled the API calls as curl output and the calls are correct. The curls are returning 200 with correct/expected content.

I have the impression that Jira API changed something from that end that the vscode extension is not trained to react to this change and cannot parse it/use it correctly.

About info:

Version: 1.76.0
Commit: 92da9481c0904c6adfe372c12da3b7748d74bdcb
Date: 2023-03-01T10:25:16.105Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Linux x64 6.1.11-76060111-generic
Sandboxed: No

[Andreas Baumgartner]

2023-03-06 14:06:40.199 [error] Error: The url must be a string.
  at n (/home/xx_username_xx/.vscode-server/extensions/atlassian.atlascode-3.0.2/build/extension/extension.js:1:1307766)
  at Ge (/home/xx_username_xx/.vscode-server/extensions/atlassian.atlascode-3.0.2/build/extension/extension.js:1:3764153)
  at Je (/home/xx_username_xx/.vscode-server/extensions/atlassian.atlascode-3.0.2/build/extension/extension.js:1:3764761)
  at /home/xx_username_xx/.vscode-server/extensions/atlassian.atlascode-3.0.2/build/extension/extension.js:1:3765459
  at Array.map (<anonymous>)
  at $e (/home/xx_username_xx/.vscode-server/extensions/atlassian.atlascode-3.0.2/build/extension/extension.js:1:3765445)
  at Ad.<anonymous> (/home/xx_username_xx/.vscode-server/extensions/atlassian.atlascode-3.0.2/build/extension/extension.js:1:4219271)
  at Generator.next (<anonymous>)
  at a (/home/xx_username_xx/.vscode-server/extensions/atlassian.atlascode-3.0.2/build/extension/extension.js:1:4216746)
  at processTicksAndRejections (node:internal/process/task_queues:96:5)

Source: Output → Remote Extension Host

‌

Version: 1.76.0 (system setup)
Commit: 92da9481c0904c6adfe372c12da3b7748d74bdcb
Date: 2023-03-01T10:22:44.506Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No

[Sean Hamstra]

Same here on macOS

‌

‌

[Jörg Bender]

Same here for 1.76.0 on Win11.

[Aaron Freeman]

Has anybody had any luck trying to downgrade their vscode version or Jira extension?

[Former user]

Hello Aaron,

yes as indicated in the ticket rollback to 1.75.x is a workaround. That’s what i did.

‌

[Aaron Freeman]

Oof, missed that. Thank you.

‌

[Dimitar Dimitrov]

Downgrading the Jira extension does not solve the problem FYI

[Chris Mulloy]

Same issue here, installing 1.75.1 over the top of the latest version worked for me as well.

[Patrick O'Lone]

Same issue - running VS Code 1.76.0 on Windows 11. Downgrading the extension from 3.0.2, 3.0.1, 3.0.0, and lastly 2.10.1 did not fix anything.

[Michael Li]

same issue

[Rickard Oscar Åkerstrand]

Reverting to 1.75.1 is a work around, until they've fixed it.

[Ville Elomaa]

same issue here

[Ricardo Gallardo]

Reverting to 1.75.1 was a nightmare with vscode server for remote development.

Had to stick with 1.76

[Brad Severs]

I think this is the same issue. I got a notification in VS Code from the Atlassian extension that a PR was created. Clicking on it to open the PR details showed this error and a ton of endless spinning circles:

‌

[Aaron Freeman]

That doesn’t seem related at all to me. This issue should be marked as resolved, as it was affecting a TON of people and has long been fixed. I’d start a new Issue if I were you Brad.

[Former user]

You're right the issue is fixed, i close the ticket.

[Vikram Kamboj]

Is anyone still facing this issue? I saw some comments here and reverted to 1.75.1 and I still see the same issue. I can’t see my Source or Destination Branches and it just keeps loading.