Unable to start work on issue
When I open an issue and try to start work on it, I get a screen with the message 'waiting for data...'. After a while I receive a message 'Looks like you've gone offline' and sometimes I get a message 'Something went wrong' with code 500 (Internal Server Error). The reason is either 'socket hang up' or something with 'eproto'.
I found this in the renderer1.log: [2019-04-04 08:26:51.719] [renderer1] [error] Repository has no issue tracker.: Error: Repository has no issue tracker. at e.exports.r.then.e.status.includes.o.then.t (/home/ramon/.vscode/extensions/atlassian.atlascode-1.1.0/build/extension/extension.js:217:4834) at process._tickCallback (internal/process/next_tick.js:68:7)
I am using Jira Cloud instead of Bitbucket Cloud for tracking issues.
Atlassian for VSCode (Official) version: 1.1.0
Visual Studio Code: Version: 1.32.3 Commit: a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4 Date: 2019-03-14T23:38:49.842Z Electron: 3.1.6 Chrome: 66.0.3359.181 Node.js: 10.2.0 V8: 6.6.346.32 OS: Linux x64 4.18.0-17-generic
Comments (8)
-
Account Deactivated -
reporter @pbusam It does happen every time when I click on
Start work on issue
. I have attached two screenshots with errors that are displayed in the developer tools console. -
reporter -
Account Deactivated @ramon15 Do you mind checking if version 1.2.1 of the extension fixes the issue?
-
reporter @pbusam Thanks for the update. I have done some research and I have come to the conclusion that the big amount of undeleted merged branches in some of my repositories causes the problem. I am not experiencing problems anymore, after I deleted the merged Git branches.
-
reporter - changed status to resolved
-
Account Deactivated @ramon15 Thanks for the feedback and glad that worked out :) Do you remember how many undeleted local branches you had for the repo? I didn't see any issues with around 100 branches on my machine.
-
reporter @pbusam I guess I had a few hundred undeleted local branches.
- Log in to comment
@ramon15 Does this happen consitently every time you click the
Start work on issue
button or only some times? Are there any other errors in theDeveloper Tools
console?