- edited description
Site credentials not being saved on Windows
Windows 7;
VS-Code: 1.38.1;
JIRA/BB-Extension: 2.1.2.
Hello everyone!
first, many many many thanks to everyone who developed such a wonderful extension! Its productive installation is one of the best things happened at my work in the last few months!!!
However, it would not be an issue, if I would not like to report a problem.
So, Jira works well directly after signing in:
However, it stops working after a restart of the VS-Code:
And if I try to refresh the list of my issues, I receive the following error message (despite I stay logged in according to the blue bar downstairs):
I am not quite sure, but I suppose that it could be a JQL-related problem, since my “Edit JQL”-window looks in the following way:
Here are my Atlassian’s settings:
"atlascode.jira.workingSite": {
"baseUrlSuffix": "atlassian.net"
},
"atlascode.jira.todoIssues.enabled": false,
"atlascode.jira.customJql": [
{
"my open issues": "assignee = currentUser() AND resolution = Unresolved order by updated DESC"
}
],
"atlascode.jira.explorer.assignedIssueJql": "assignee = currentUser() AND resolution = Unresolved order by updated DESC",
"atlascode.jira.explorer.openIssueJql": "assignee in (EMPTY) AND resolution = Unresolved order by updated DESC",
"atlascode.jira.jqlList": [
{
"id": "XYZ-417d-XYZ-832e-1db034717aac",
"enabled": true,
"name": "My open xyz.xyz.com issues",
"query": "assignee = currentUser() AND resolution = Unresolved order by updated DESC",
"siteId": "xyz.xyz.com",
"monitor": true
}
],
"atlascode.jira.lastCreateSiteAndProject": {
"siteId": "xyz.xyz.com",
"projectKey": ""
},
"atlascode.bitbucket.issues.createJiraEnabled": true,
Thank you in advance!!!
Comments (33)
-
reporter -
reporter - edited description
-
Account Deactivated @Gleb Savateev Could you open “Preferences:Open Settings(UI)” and search for “level” and then make sure “Atlascode: Output Level” is set to debug.
Then go to the Output tab in the bottom pane and choose “Atlassian” from the selectbox on the right and tell me if there are any errors in the console when this happens?
-
reporter @{557057:3695b794-cde3-43a2-99aa-c0fc6151b754}
Done!
BTW, we use a hosted JIRA/BB-Service.
Thank you in advance!
PS: If I delete the saved JIRA-authentification and sign in once again, then it works again, but only until the next restart of the VSCode.
-
@Gleb Savateev , can you check in the Windows Credential Manager and see if there are any entries whose name has “atlascode” in it?
-
reporter @Nick Rundquist , sorry for such a late response, I was, unfortunately, sick:(
Here are the corresponding entries:Thank you in advance!!!
-
I’ve got the exact same issue!
Only this is my setup according to VS code
Version: 1.39.2 (system setup)
Date: 2019-10-15T15:35:18.241Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17134 (Windows 10) -
@PurpleHeart , are you also using the Server version of Jira or Bitbucket?
-
Yes, it’s a ‘custom Jira site’ , a global company setup Jira ;). @Nick Rundquist
-
- changed title to Site credentials not being saved on Windows
-
- changed status to open
-
We’ve identified the root cause here, thanks for bringing this to our attention.
-
Thanks for the update! And even better for finding the root cause!
-
reporter @Nick Rundquist Thank you very much!!! Looking forward to try you the fix out:)
-
Is there any update on when a fix will be available ? @Nick Rundquist
-
Version 2.1.5 is on the marketplace now and should solve the issue. Let me know if you’re still having problems.
-
reporter @Nick Rundquist Thank you very much for the information, but the problem is, unfortunately, still here, with all the same symptoms described above.
However, the screenshot of the credentials manager seems to look different this time:
Thank you for your help!
-
After the reload the extension did work. However I just restarted and it’s again saying ‘r.GetFields is not a function’ on opening the extension.
-
Same issue on macOS 10.15, VSCode 1.40.1, atlascode 2.1.5. We’ve got a self hostet JIRA. And in case I setup the server account, the first fetch is running fine. Coming back to the Jira view will bring the error r.GetFields in the Jira Issues view and .getJqlDataFromPath in the JQL config view.
Seems to be that the configured Jira and Bitbucket custom site configs will disturbe each other.
What have I done in front of the test:
- Removed all caches from VSCode
- Reinstalled atlascode plugin
As I started the plugin again, the configurations were already there. So I removed all configured server for Jira and bitbucket.
We are using a self hosted Jira and Bitbucket server, both with the same domain and different context pathes (/jira, /stash).
Then I reconfigured Jira with the custom Jira page and Context Path /jira
Added the login credentials and waited to see the first incoming issues from standard JQL. All is running fine.
Then I configured Bitbucket with Context Path /stash and the login credentials.
Now the Jira issues run into trouble with the loose ends of the internal client (error getFields etc.)
So only Bitbucket Pull requests are running fine.
If I delete Bitbucket server config, Jira is running fine again.
-
Reopening this on our end. I’ll take a second look.
-
I am facing the same issue as per the description by @Florian Schebelle . While our Jira server and Bitbucket server has a similar setup, they are hosted under the same hostname with different context path.
Is that the root cause since the ClientManager stores client objects by hostname as key into the _clients map? I guess the Jira client object got overwritten when we setup the Bitbucket credentials.
-
My situation is similair to Thomas Lee. The hostname is similair, the context path is different. Also Jira keeps working if I disable / don’t configure the Bitbucket settings.
-
@Thomas Lee @PurpleHeart ,
We released version 2.2.0 today with a fix for the issue with multiple instances with the same hostname.
-
@Gleb Savateev , was your issue the same as the others, where you had Bitbucket and Jira servers on with the same hostname?
-
macOS 10.14.6, vscode 1.40.2, atlascode 2.20
I have Bitbucket and Jira on the same host under different context paths too — the issue is still reproducible for me.
If it matters, I also set up certificates to be used for accessing the corresponding host.
-
I’m still not able to use both Jira & bitbucket. Same error.
Directly when logging out of Bitbucket the Jira part works again.
-
reporter @Nick Rundquist , yes, my issue is completely the same. I have update the extension to the newest version today (2.20) and, unfortunately, the issues is still there.
-
https://bitbucket.org/atlassianlabs/atlascode/downloads/atlascode-2.2.2-hostnamefix.vsix
Would one of you be willing to download this build and let me know if it fixes the issue? It should, but I want to be sure this time. You can install extensions from the filesystem by going to the Extension explorer, selecting the “…” menu in the upper right and selecting “Install from VSIX…”.
-
@Nick Rundquist , works fine for me, thanks.
-
Now works as expected. :-)
-
reporter @Nick Rundquist , the build works brilliant! The gates of awesome are opened even brighter right now, thank you very much! Looking forward to get the official 2.2.2!
Have a nice day!
-
- changed status to resolved
And now the fix is included with the newly released 2.3.0.
Thanks for everyone’s patience and help getting this one fixed.
-
reporter @Nick Rundquist , thank you very much! Awesome work!!!
- Log in to comment