You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please do not alter or delete the original description. The survey telemetry uses the ADO description to parse some important pieces of information.
Please take the following steps to make sure the workitem is triaged correctly –
Please review the comments, if available, and/or the logs and use your judgement to align the workitem to the appropriate Area Path.
If no comments are available, please use these 2 links to get more data from UI and Service side logs to investigate further:
Analysis tool: Link To analyze, please copy the session id and paste to feedback dashboard. Session id: OKRKl
Service side logs: Link
Email provided:
If email is available, please reach out to the user to get more information on the issue
To ensure correct reporting tag the workitem with one of the five categories:
Tag as Documentation, FeatureGap, Quality, Usability, or Performance.
Add an estimated timeline tag depending on the effort and priority of the item
Tag as ShortTerm, MediumTerm, or LongTerm.
If the workitem is still unactionable even after reviewing the comments and logs, please tag the item as “NotActionable” and mark it as Removed (instead of Done).
Please use this customer specific info for further investigation:
SubscriptionId: 5fea1bce-43ac-496d-b826-b0d56cd9b209
Resource Group: aalab-mlworkspace-insurancepii
Workspace: aalabmlworkspaceprodinspii
Survey Time: 2022-01-18T14:41:09.296Z
Session_Id: OKRKl
source:
comments: Documentation is not clear enough Integration with VS code fails a lot Project folder structure that works in VSCode does not works properly in Azure
action:
rating: 7
path: /data
To analyze, please copy the session id and paste to feedback dashboard
session id: OKRKl
Analysis tool: Link
Service side logs: Link
The text was updated successfully, but these errors were encountered:
Bug id: 1587639
Please do not alter or delete the original description. The survey telemetry uses the ADO description to parse some important pieces of information.
Please take the following steps to make sure the workitem is triaged correctly –
Please review the comments, if available, and/or the logs and use your judgement to align the workitem to the appropriate Area Path.
If no comments are available, please use these 2 links to get more data from UI and Service side logs to investigate further:
Analysis tool: Link To analyze, please copy the session id and paste to feedback dashboard. Session id: OKRKl
Service side logs: Link
Email provided:
If email is available, please reach out to the user to get more information on the issue
To ensure correct reporting tag the workitem with one of the five categories:
Tag as Documentation, FeatureGap, Quality, Usability, or Performance.
Add an estimated timeline tag depending on the effort and priority of the item
Tag as ShortTerm, MediumTerm, or LongTerm.
If the workitem is still unactionable even after reviewing the comments and logs, please tag the item as “NotActionable” and mark it as Removed (instead of Done).
Please use this customer specific info for further investigation:
SubscriptionId: 5fea1bce-43ac-496d-b826-b0d56cd9b209
Resource Group: aalab-mlworkspace-insurancepii
Workspace: aalabmlworkspaceprodinspii
Survey Time: 2022-01-18T14:41:09.296Z
Session_Id: OKRKl
source:
comments: Documentation is not clear enough Integration with VS code fails a lot Project folder structure that works in VSCode does not works properly in Azure
action:
rating: 7
path: /data
To analyze, please copy the session id and paste to feedback dashboard
session id: OKRKl
Analysis tool: Link
Service side logs: Link
The text was updated successfully, but these errors were encountered: