Atlassian vscode question: When selecting "Start Work" on an issue. Source branch is not populated.
Asked by llignhoj:

This is a question about the Atlassian vscode plugin.

When I start work, I see that the Repository field is set correctly, but "Source Branch" is empty with "No branches found", Clicking the drop-down displays "None".

What am I missing setup wise?


Answers:
author: Sam Ware
body: Not sure. But mine was working and it has started not working. Not sure it is because the most recent update which I recently applied.

comments: author: Sam Deane
body: +1 here - I also had it working and now it mysteriously isn't, and I'm not aware of having changed anything


author: Trent Manganello
body: Same here. It was working on March 1st, but appears to no longer be working for me.


author: Daniel Tullis
body: Same problem. Was working fine last week.


author: Vani Thilagar
body: Ditto here


author: Alexander Holzleitner
body: Same problem. "no branches found"


author: Alex Robillard
body: Same problem. :(


author: Rickardo Hyde
body: Same problem here. smh


author: Marco Guinter Alberton
body: Same problem here.


author: Marco Guinter Alberton
body: The issue is occurring in VSCode version 1.76. I downgraded to version 1.75.1 and the problem does not occur.

If you also want to dowgrade:  
1) first disable automatic update in settings (Ctrl + , or Cmd + ,) look for Update:Mode and change it to manual.  
2) Download version 1.75.1 from the official website appropriate for your environment: <https://code.visualstudio.com/updates/v1_75>  
3) Install VSCode 1.75.1.

Done!  

Hopefully the issue will be resolved in version 1.77...


author: Rickardo Hyde
body: [@Marco Guinter Alberton](/t5/user/viewprofilepage/user-id/1196882) downgrading works for me. Thanks


author: Sean Corfield
body: It's strange since Atlassian extension 3.0.2 has been out for weeks (and was working fine until a few days ago), but I tried rolling back to 3.0.1 anyway -- and that still couldn't find source branches.

I tried updating git, (from 2.25.0 to 2.39.2) just in case that was affecting it -- nope.

But the regular git support in VS Code can find the source branches just fine.


author: Alex Robillard
body: [@Marco Guinter Alberton](/t5/user/viewprofilepage/user-id/1196882) This worked! Thank you!


author: Agnius Bartninkas
body: Same here. Did not work since last week. Downgraded according to the suggestion of [@Marco Guinter Alberton](/t5/user/viewprofilepage/user-id/1196882) and it now works fine. Thanks.

Hope it gets resolved in a later update.


author: Yusif Jasim
body: Same this occurred to me. Thanks for your suggestion [@Marco Guinter Alberton](/t5/user/viewprofilepage/user-id/1196882), it worked.


author: Agnius Bartninkas
body: Strangely enough, even when I set my update mode to manual in VSCode, it still updates automatically and I get to downgrade it more or less every day. It really is getting annoying.


author: Chris Yaskoski
body: Also impacted and wasted an hour on it this morning thinking I had done something, hope they can resolve soon.


author: Sam Ware
body: I saw a pull request for this today. Not sure where this gets rolled to the VSCode Marketplace

<https://bitbucket.org/atlassianlabs/atlascode/pull-requests/1051>


author: Sean Corfield
body: It's merged and tagged 3.0.3 so I'd expect it to show up in the marketplace fairly soon...?


author: Sam Ware
body: Version 3.0.3 is now available and I just confirmed that it works as before.


author: Sean Corfield
body: Sam, is Create Pull Request working for you now?

I get:

Error creating pull request

Cannot read properties of undefined (reading 'site')

With VS Code 1.77 and Atlascode v3.0.3.

I can Start Work to create the Branch from a Jira ticket now, but still can't Create Pull Requests like I could before.


author: Sean Corfield
body: Perhaps stranger still: I can create pull requests using the extension in one workspace but not in the other.

The non-working workspace / repo was working fine before this whole debacle.

I can do "start work" in both and create branches.

Any ideas for debugging this out somehow resetting the workspace / repo setup?


author: Jameesh Moidunny
body: Had the same issue , V1.77.2 resolved this and working fine now


author: Damian Shaw
body: The tracking issue for it should be here: <https://bitbucket.org/atlassianlabs/atlascode/issues/983/vscode-176-start-work-displays-no-branches>

But it seems the issues on the repo have been made private a few days ago when a bot started heavily spamming it. Last I saw there was no response from Atlassian.

As others have said this started in VS Code 1.76 so a workaround is to downgrade to 1.75.1, unfortunately there are big fixes/features in 1.76 that I would prefer not to downgrade.

comments: author: Sam Ware
body: I agree with the not downgrading. Hopefully, they resolve soon. This feature made working with Jira much easier.


author: Marty Cochrane
body: Thanks for the link, unfortunate it's been made private. I also don't wish to downgrade VsCode as I use it with other projects that don't need to deal with JIRA. Guess we wait.


author: Damian Shaw
body: FYI I've setup an alert for any new commits or PRs on the repo: <https://bitbucket.org/atlassianlabs/atlascode/src/main/>

If anyone has a commercial relationship with Atlassian it would be great if you could file a ticket and let us know the status.


author: Marty Cochrane
body: I've asked my IT department, I'll let you know if we make any progress.


author: Damian Shaw
body: I see a PR has been opened ?: <https://bitbucket.org/atlassianlabs/atlascode/pull-requests/1051/vscode-1423-fixed-the-git-refs-stuff>

comments: author: Damian Shaw
body: Released now as 3.0.3! <https://marketplace.visualstudio.com/items?itemName=Atlassian.atlascode>

You will need VS Code 1.77 or higher.


author: Vani Thilagar
body: Thank you! It works correctly. What a relief finally!


author: Mike
body: Confirmed! Thank you so so much for giving me my workflow back!! ?


author: Sam Ware
body: Version 3.0.3 is now available (just release) and I just confirmed that it works as before.


author: Marco Guinter Alberton
body: I've now updated to VSCode version 1.77.3 and Jira and Bitbucket (Atlassian Labs) version 1445536 and it's resolved, working fine now as expected.

<br />

This revision is large and many issues have been resolved, but I couldn't find a specific comment about it in the release notes as well as on GitHub.

<br />

The important thing is that it was resolved. Enjoy!


author: nikitab
body: Looks like the issue was fixed. Works fine for me now!  
Thank you!

P.S. I didn't update anything or downgrade previously


author: Luke Pritchard
body: Yup still having this issue, on VS Code 1.76.2


author: Justin Johnson
body: Azure DevOps services works as expected.


author: Justin Johnson
body: Same issue here. Still not resolved.


author: Luca Saba
body: You mean downgrade VSCode, not just the plugin... WOW....that's hard...

comments: author: Marco Guinter Alberton
body: Yes, unfortunately. But works for now. Obviously isn't real solution, just while Atlassian or Microsoft solving the strange behavior.


author: Damian Shaw
body: [@Marco Guinter Alberton](/t5/user/viewprofilepage/user-id/1196882) FYI Microsoft aren't doing anything about this: <https://github.com/microsoft/vscode/issues/176700>


author: Sam Ware
body: Someone is working on this.

<https://bitbucket.org/atlassianlabs/atlascode/pull-requests/1051>


author: Mike Dunn
body: Same issue here, downgrading worked for me as well.


author: Adam Cooke
body: Same issue, downgrading to 1.75.1 worked. Please can Atlassian make some progress on this.


author: Bela Finkelshtein
body: I had same issue. Downgrade worked. Thanks!


Tags: bitbucket-server

server

vscode