Can't create a new issue
When creating a new issue only “waiting for data …” shows up. In developer tools where a message “[Embedded Page] Uncaught TypeError: Cannot read property 'fields' of undefined”
vscode: 1.33.1
plugin: 1.2.3
MacOS: 10.14.3
Comments (21)
-
Account Deactivated -
reporter Yes, every time, even after restart. You‘re right, it looks like an error handling problem.
-
Account Deactivated @tomfxs Can you install v 1.3.0 of the extension and see if it at least gives you an error message and possibly a custom field issue report to click on?
-
reporter Hi @{557057:3695b794-cde3-43a2-99aa-c0fc6151b754} I’m sorry, I’ve tested with 1.3.0 and 1.3.1, but still the same:
[Embedded Page] Uncaught TypeError: Cannot read property 'fields' of undefined, webviewElement.ts:392
noting else …
-
Account Deactivated - attached atlascode-1.3.3-issuetypedebug.vsix
@tomfxs I’ve created a new version for you to use to help me debug. It probably won’t fix the issue, but if you can install it temporarily and try again it should at least give us an idea of what’s going on.
Please follow these steps:
download the attached vsix file
in VS Code, go to the Extensions sidebar, click the … menu and choose “install from vsix”
Once installed, restart VS Code
open up the create issue screen
open the help menu and choose “Toglle Developer Tools”
In the dev tools console, you should see a dump of the issuetype screens. Could you add that output to this page? (you can scrub any sensitive names/data).
-
Account Deactivated -
assigned issue to
-
assigned issue to
-
reporter @brainicorn Sorry for the late answer, please see the attached screenshot.
-
reporter -
Account Deactivated - attached atlascode-1.3.4-issuetypedebug.vsix
@tomfxs Sorry to make you install another vsix file. Could you please install this one and then:
- open the command palette
- search for "Atlassian: Create Issue Meta"
- run the command
- In the "Output" tab in the bottom panel, use the dropdown to select "Atlassian"
You should see a really large JSON blob. Could you please send me that? It contains the low-level data we use to render the create issue screen. With that blob, I'll be able to debug using the fields returned by your Jira.
Thanks!
-
Issue
#131was marked as a duplicate of this issue. -
reporter Hi @{557057:3695b794-cde3-43a2-99aa-c0fc6151b754} , sorry for the delay! “Atlassian: Create Issue Meta” has no effect, it doesn’t do anything at all …
But I noticed that it works on my laptop, so I deactivated all other extensions on my desktop, but it still doesn’t work …
On my laptop there is a message: “non-renderable fields detected, View a problem report”, see attachment, what it shows.
Maybe this helps? -
Account Deactivated @Thomas Sauter That’s really strange that it works on one machine and not another. Are you desktop and laptop running the same OS?
Can you tell me the OS+version on both machines?
Also, do you get the create meta json in the Atlassian output if you run that command on your laptop?
-
reporter Both macOS 10.14.3
Where is no “Atlassian” In the Output-Tab
-
Account Deactivated You should be able to find the Atlassian output like this:
-
Any updates on this?
I cannot create Jira issues through the plugin it just freezes on ‘waiting for data…’ and I get a Uncaught TypeError in the console
I’m on version 1.4.3
MacOS 10.14.4
vscode 1.37.1
-
reporter Still the same with 1.38.0
-
Same problem here too.
Version: 2.0.2
Version: 1.38.1
Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0
Date: 2019-09-11T13:30:08.229Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 5.0.0-29-generic
-
Account Deactivated Linked to VSCODE-762
-
Account Deactivated - changed component to triaged
-
Account Deactivated - changed status to resolved
We believe this is fixed in 2.0.3 which is now available from the VS Code Marketplace.
Please re-open if needed.
-
- removed component
Removing component: triaged (automated comment)
- Log in to comment
@tomfxs Does this happen every time? If you restart vscode and try again, does it work?
I have a feeling it’s just a lack of error handling when we make a request to get the available fields from Jira which may be an intermittent problem.