Use 'workbench.action.openIssueReporter' to report issues for the extension

[dgolovin]

Here is an example for Python extension.
https://github.com/microsoft/vscode-python/blob/ce62901d594bf222b3a3f827b5c8998d54ba901a/src/client/common/application/commands/reportIssueCommand.ts#L100

[msivasubramaniaan]

@degolovi I need some clarification on this issue

• Which link you clicked for the attached popup open?

• Where we need the issue report on our extension?

• Why we need it?

[dgolovin]

To open report window use

[dgolovin]

We already have it here

and as a navigation button in Application explorer

All this to get user feedback right from vscode window.

[rgrunber]

I agree here. We should be using the platform's issue reporting API and pre-filling it with values that make it relevant for us. I think it's a little nicer than the current approach which just uses the bugs property in the package.json to generate a url and pass it to vscode.open command with a query string.

[msivasubramaniaan]

I agree here. We should be using the platform's issue reporting API and pre-filling it with values that make it relevant for us. I think it's a little nicer than the current approach which just uses the bugs property in the package.json to generate a url and pass it to vscode.open command with a query string.

@dgolovin and @rgrunber
Trying to achieve something here. Here attached the reference screen and the issue which created through workbench.action.openIssueReporter

Will try to customize the screen in terms of width and height and other items if possible. Also used issueReport.md for the body content. Let me know if anything needs to added on it as well.