Jira & Bitbucket extension for VS Code doesn't remember authentication credentials

[Greg Ferrari]

I use Visual Studio Code (VS Code) as an editor for writing software on Widows and linux.  Atlassian has a free extension for VS Code that allows you to connect to and interact with Jira and Bitbucket.  I have installed this extension,entered the URLs of my Jira and Bitbucket data center instances as “custom sites” (vs. Jira and Bitbucket Cloud), and entered my username/password credentials for those instances.  VS Code successfully connects to both Jira and Bitbucket; I can see Jira issues, Bitbucket pull requests, etc.

Here’s the problem, when I close VS Code and reopen it, VS Code no longer connects to Jira or Bitbucket.  If I click on the “Sign in to Jira/Bitbucket” buttons on the status bar, it simply drops me on the settings page that allows me to add a custom URL.  It isn’t using the credentials I entered when I first added the URL, and there is no way that I have found to get it to prompt me for credentials again.  I can see the URL I entered originally, but there’s no option to initiate a manual connection or re-enter my credentials.  I am forced to delete the URL I entered the first time, and add it all over again.

Is this expected behavior?  How can I configure Atlassian extension for VS Code to automatically connect to Jira/Bitbucket, or at least prompt me for just my password instead of making me completely reconfigure the connections?

I'm using "Jira and Bitbucket (Official)" extension version 2.3.1 and VS Code version 1.41.1 on Red Hat Enterprise Linux 7.

On Windows 10, the Bitbucket side of things in the extension seems to work.  On the Jira side, the extension connects but never shows any results where I should see Jira issues listed.

[Marlon Aguiar · Accepted solution]

Hi Piotr,

Yes as long as he still included in any groups/project roles for the notification scheme on the project he would still recieve notifications.

In order for a user not recieve any notifications the best thing would be to remove it from all groups.

Hope it helps!

Regards,
Marlon

[Nic Brough -Adaptavist-]

Might do.

Users should only get emails from Jira if they can see the issue that is generating the notifications. There are two possibilities:

1. You're using a plugin or code that bypasses this security. (Actually, a lot of people keep asking for this, and it's a security nightmare because they have not thought through the implications. Jira won't do it off the shelf, because it's better to be secure by default)

2. You have set up issues with "anonymous" access - that implies the whole world can see the issue, so Jira will happily send email to someone who has no application access. Because it's public.

Edit - oops, yes, see other answer - I was assuming "no application access" meant you had removed the user from all roles and groups - that's standard practice everywhere I've been, but I should not assume that.