vscode extension no longer works for new PR

[lpravda]

Hello, community, I've recently started having trouble using, otherwise excellent, vs code Atlassian extension.

my setup

mac os: 13.2.1

vscode: 1.76.2

extension v: 3.0.2

When trying to make PR from inside of vs code, I can't get the list of branches to load. Clicking on the field with source/target branch in the past populated autocomplete that even suggested what source and target branch should be. Now all I see is "Loading..." in the context but the list never loads. One cannot even put in a branch name manually, so this feature is effectively unusable. I could not see anything in the vscode log. Downgrading extension to older version does not work as well.

Any advice?

Thank you

Lukas

[lpravda]

Another month has passed. Is there any update on this?

[Ricardo]

Hello @Patrik S 

The issues stated by @lpravda has still not been fixed till today.

* commit messages are no longer loaded when creating PR.

* list of reviewers does not populate at all.

* when trying to confirm the PR an error: `Cannot read properties of undefined (reading 'site')` appears.

Is there any update?

[lpravda]

Hello Patric,

I must say the issue was fixed, nevertheless, the extension remains useless.

Specifically:

* commit messages are no longer loaded when creating PR.

* list of reviewers does not populate at all.

* when trying to confirm the PR an error: `Cannot read properties of undefined (reading 'site')` appears.

Would be great if these issues were fixed so that the extension can be again a powerful tool to interact with Atlassian products.

[Maciek]

Go see https://jira.atlassian.com/browse/API-675 

[Marcus Thelin]

I cannot even view my issue in vscode. I just get a blank screen and in the developer console this error is thrown. I have the latest vscode and extension versions.

[Patrik S]

Hello @lpravda ,

Welcome to the community!

We have received some other reports that the VSCode extension Jira and Bitbucket (Atlassian Labs) is not fully working on the latest release of VSCode - version 1.76.* (February 2023). It seems like this VSCode release has introduced some changes that are affecting the functionality of the extension, more specifically the extensions if not able to find any branches to be selected in the dropdowns, for example, when creating a pull request or starting work in a Jira issue.

Our engineering team is currently investigating this issue and working on a fix. As a workaround, you can downgrade the version of your VSCode to 1.75.1, where the extension should be working as usual. The VSCode 1.75.1 can be downloaded using the following link: 

• https://code.visualstudio.com/updates/v1_75

Thank you, @lpravda !

Patrik S

[Maciek]

Anybody having issue with PR not working please go see https://jira.atlassian.com/browse/API-675 and click on "This affects my team"

[Peter Hand]

Go see https://jira.atlassian.com/browse/API-675

[Peter Hand]

If the `Cannot read properties of undefined (reading 'site')` is affecting you when creating a PR from VS  Code, go and update the "Affected Customers" and start watching this issue:

https://jira.atlassian.com/browse/API-675

[Scott Anderson]

Unfortunately, the extension is also not working for me (specifically, the reload button does not seem to have any effect on actually reloading the issues/pipelines/PRs)

[JoeyBerger]

@lpravda I agree...this fix is pretty sub-standard and essentially makes the extension useless.

[Lee Wilkins]

Still no news on a fix for this yet? The extension is completely broken as @lpravda comments on 6th April

[Vytenis Kučiauskas]

All my comments on how to fix it and where the problem is - were deleted - so I can't help it anymore. I created a pull request for the fix and it also was deleted. suggestion - wait

[Patrik S]

Hello @MXB08M9 ,

thank you for reaching out and reporting this.

I was able to reproduce this issue in the most recent version of the Jira and Bitbucket (Atlassian Labs) VSCode extension v3.0.13.

I am in contact with the engineering team managing the extension to report this issue.

Meanwhile, as @lpravda mentioned, I have confirmed that version 3.0.12 of the Atlassian extension is not affected by this problem, so I'd suggest installing that specific version until a fix for the latest one is released.

To install a specific version of the extensions in VSCode : 

1. Navigate to the Extension view by clicking in the Extensions button in the left sidebar.
2. Select the Atlassian extension
3. In the dropdown right after the Uninstall button, click on Install specific version
4. From the list of versions, select v3.0.12.
5. Restart VSCode or use the Restart extensions button.

I hope this helps! Let us know in case you have any questions.

[lpravda]

That's because they broke it again in the latest release 3.0.13... You have to downgrade to 3.0.12. That one still works.

@Patrik S Do you think this is something your team could fix? Thank you

[MXB08M9]

i am having the same issue now - cant create PR

[yakirgb]

@lpravda @JoeyBerger I found possible solution, replace "ssh://" with "https://" on "<repo>/.git/config" solved my issue. 

[Patrik S]

Hello @Damian Shaw ,

Our development team has released a new version of the Jira and Bitbucket (Atlassian Labs) (v3.0.3) which contains the fix for the issue where branches were not being listed. 

To install the new version of the extension you will need also to update your VSCode to the release 1.77+.

Thank you, @Damian Shaw !

Patrik S

[Damian Shaw]

I see a PR has been opened just now: https://bitbucket.org/atlassianlabs/atlascode/pull-requests/1051/vscode-1423-fixed-the-git-refs-stuff 🎉

[Damian Shaw]

@Patrik S there are a significant number of responses here but no one has officially responded: https://community.atlassian.com/t5/Bitbucket-questions/Atlassian-vscode-question-When-selecting-quot-Start-Work-quot-on/qaq-p/2286800

Also the issues on repo has been made private (happened about 1 month ago) so it's not possible to see if it's officially acknowledged as an issue: https://bitbucket.org/atlassianlabs/atlascode/jira

Also @Vytenis Kučiauskas managed to identify the issue but does not have permissions to post a PR or raise an issue against the correct repo, so has tried raising the attention of the Atlassian team in several places, e.g. https://bitbucket.org/FDisk/atlascode/pull-requests/1 

Apparently his comments and other attempts to highlight the issue were deleted (his comment below).

[Tom Badran]

<deleted>