Can't configure

[Martin Hutník]

VS Code Version: 1.33.1
Atlassian for VSCode Version: 1.2.2
OS: Windows_NT x64 10.0.17134

I can’t configure the plugin. When I open the command palette and run the following commands, small error window pops up at the bottom right corner of the window.
Atlassian: Open Welcome - command ‘atlascode.showWelcomePage' not found
Atlassian: Open Settings - command 'atlascode.showConfigPage' not found
etc…
none of the commands work

[Jonathan Doklovic]

@aqua-hum Did you receive any error notifications when the extension was installed?

Sounds like something went very wrong during the install.

Can you try removing it and re-installing?

[Martin Hutník]

No errors recieved during the install. I tried reinstall the plugin, disable all other plugins, but nothing worked so far.

[Maurício Duarte]

@Martin Hutník did you resolve your issue? Same problem here

[Jonathan Doklovic]

Does this still happen with extension version 1.3.x?

[Pramod Busam]

Can you try updating to version 1.4.0 of the extension and see if that fixes this issue. (Please note that you need to update to VS Code 1.34 to use this version)

[Maurício Duarte]

It was fixed to me. Thank you

[Елисеев Алексей]

Hello. The plugin does not work in an isolated network without access to the Internet. It seems that the plugin needs Internet access to download the html files for the settings window. Could you distribute VSIX file with packed html files?

[Pramod Busam]

Could you check if you are on the latest version of the extension (1.4.2) and if there are any errors in VS Code’s developer tools console?

The settings page itself does not need internet access, but in order to authenticate, you need to grant access for the extension on Jira or Bitbucket website which is opened in a web browser. Apart from that, the extension uses the REST api of Jira and Bitbucket for pretty much all the features, so that would need internet access too.

I will close this issue as the problem causing the initial issue is fixed and you may be experiencing a separate issue. Please open a new issue if needed.