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
Copy file name to clipboardExpand all lines: docs/ide/how-to-report-a-problem-with-visual-studio.md
+31-59Lines changed: 31 additions & 59 deletions
Original file line number
Diff line number
Diff line change
@@ -15,105 +15,77 @@ ms.workload:
15
15
> [!NOTE]
16
16
> For Visual Studio for Mac, see [How to report a problem in Visual Studio for Mac](/visualstudio/mac/report-a-problem).
17
17
18
-
You can report a problem from either Visual Studio or its installer by using the Feedback Tool included in them. The Feedback Tool enables you to easily include diagnostic information in your feedback and helps Visual Studio teams to diagnose and fix issues much more effectively. Here are the steps to report a problem.
18
+
You can report a problem from either Visual Studio or its installer. The built-in Feedback Tool allows you to easily add diagnostic information that helps the Visual Studio teams diagnose and fix the issues. Here are the steps to report a problem.
19
19
20
20
1.**In Visual Studio**, select the feedback icon in the upper-right corner and select Report a Problem. You can also access the feedback tool from the menu **Help** > **Send Feedback** > **Report a Problem**.
21
-
21
+
22
22
Alternatively, report a problem in **Visual Studio Installer** if you can't install Visual Studio or are unable to access the feedback tool within Visual Studio. In the Installer, select the feedback icon in the upper-right corner and select Report a Problem.
23
23
24
24
25
-
1.If not signed in, select **Sign In**as shown in the following screenshot. Follow the instructions on-screen to sign in.
25
+
1.Clicking **Report a Problem**will open your default browser and sign you in using the same account you use to sign in to Visual Studio
26
26
27
-
27
+
28
28
29
-
Not only can you report a problem when you are signed in, but you can also vote and comment on any existing feedback.
29
+
1. Start by entering the descriptive title of your bug report. It must be at least 25 characters long.
30
30
31
-
1. Once signed in, you will be able to see your **Problems** and **Activity** on the **Items I follow** screen
31
+
32
32
33
-
33
+
1. Once you start typing, possible duplicates are shown under the title field
34
34
35
-
1. Visual Studio provides an interface to search for your problem and see if others have reported it. If someone has reported it, "up-vote" it to let us know.
36
-
> [!NOTE]
37
-
> In order to search, please input the desired text into the search box and either click Enter or press the Search icon.
35
+
38
36
39
-
37
+
1. Select the possible duplicate bug reports to see if there is one matching your own problem. If there is, vote for it instead of creating your own ticket.
40
38
41
-
1. If you don't find the problem you encountered, choose **Report new problem** at the bottom of the screen.
39
+
42
40
43
-
1. Create a descriptive title for the problem that helps us route it to the correct Visual Studio team.
41
+
2. If no duplicates were found, continue by entering a description of the problem. It's important to be as clear as possible to increase the chances of us being able to reproduce the bug. Make sure to include clear reproduction steps.
44
42
45
-
1. Give us any additional details, and if possible, provide us with the steps to reproduce the problem.
43
+
3. If relevant to the bug report, take a screenshot by checking the *Include Visual Studio screenshot* checkbox.
46
44
47
-
45
+
46
+
*Only Microsoft engineers can see the screenshot*
48
47
49
-
1. Select **Next** to move to the **Attachments** tab. Here, you can capture your current screen to send it to Microsoft. To attach additional screenshots or other files, choose **Attach Additional Files**.
48
+
You can even crop the screenshot directly in the browser to remove any sensitive or unrelated parts.
50
49
51
-
50
+
4. One of the best ways to help the Visual Studio engineering team solve the problem, is to provide a trace and heap dump files for them to look through. You can easily do that by recording the steps that resulted in the bug.
52
51
53
-
1. If you don't want to attach a screenshot or [record a repro](#record-a-repro), select **Next** to move to the **Summary** tab.
52
+
53
+
*Only Microsoft engineers can see the recording*
54
54
55
-
1. Select **Submit** to send your report, along with any images and trace or dump files. (If the **Submit** button is grayed out, make sure that you've provided a title and description for the report.)
55
+
5. Review the attached files and upload additional files if you believe it would help diagnose the issue.
56
56
57
-
For information about what data is collected, see [Data we collect](developer-community-privacy.md#data-we-collect).
*Only Microsoft engineers can see the attached files*
58
59
59
-
## Record a repro
60
+
6. The last step is to hit the **Submit** button. Submitting the report will send it directly into the internal Visual Studio bug reporting system awaiting triage.
60
61
61
-
Trace and heap dump files are useful in helping us diagnose problems. We appreciate it when you use the **Report a Problem** tool to record your repro steps and send the data to Microsoft. Here's how to do so:
62
+
## When further information is needed
62
63
63
-
1. After you enter a title and description for your problem, select **Next** to move to the **Attachments** tab.
64
+
When an issue is missing important information, we assign the **Needs More Info** state. We comment on the issue with the specific information we need, and you'll receive an email notification. If we don't receive the information within seven days, then we send you a reminder. After that, we close the ticket after 14 days of inactivity.
64
65
65
-
1.Select the **Record**tab.
66
+
1.Follow the link in the email to the problem report or go to My Feedback to see all reports in the **Needs More Info**state.
66
67
67
-
1. Under **Record your actions**, select the current instance of Visual Studio if you can reproduce the problem there. If you can't, for example if Visual Studio stops responding, select **\<Create a new instance>** to record the actions in a new instance of Visual Studio.
1.Select **Start Recording**. Give permission to run the tool.
70
+
1.Selecting the Provide More Info link on the problem report navigates you to a new screen. From here, you can see what info is being requested.
70
71
71
-
72
-
73
-
1. When the **Steps Recorder** tool appears, perform the steps that reproduce the problem.
74
-
75
-
1. When you're done, choose the **Stop Record** button.
76
-
77
-
1. Wait a few minutes for Visual Studio to collect and package the information that you recorded.
78
-
79
-
For information about what data is collected, see [Data we collect](developer-community-privacy.md#data-we-collect).
80
-
81
-
## When further information is needed (Need More Info)
82
-
83
-
Starting in Visual Studio 2017 Version 15.5, there's a new workflow to help users provide additional information about problem reports.
84
-
85
-
1. When a Microsoft engineer sets the [Visual Studio Developer Community](https://developercommunity.visualstudio.com/) problem to the **Need More Info** state, any user that posted, voted, followed, or commented on the problem gets a notification in the **Report A Problem** tool in Visual Studio.
86
-
87
-
88
-
89
-
1. Click on the **View Problems** link to filter and sort the view to the problems that need attention. These problems also have an indicator next to them, to differentiate them in general search.
90
-
91
-
1. Click on a problem to see the problem details view.
92
-
93
-
94
-
95
-
1. To view the **Need More Info** request, click the **View their request and respond** link in the problem details view. A dialog box shows the request.
96
-
97
-
1. You can provide more information by adding comments, attachments, or recording steps. This experience is similar to reporting a new problem or providing additional information when voting on a problem.
100
75
101
76
1. The requesting Microsoft engineer receives a notification about the extra information provided. If they have enough information to investigate, the problem state changes. Otherwise, the engineer asks for even further information.
102
77
103
-
> [!NOTE]
104
-
> * When you reply, the notification goes away. In its place, you see a banner that thanks you and facilitates a way to provide even more information.
105
-
> * Once the issue changes state, the notification goes away for everyone that's following the issue.
106
-
> * More than one person can reply on the same **Need More Info** request.
107
-
> * There isn't a **Need More Info** workflow on [Developer Community](https://developercommunity.visualstudio.com/) when you access it directly through a web browser, but you can also provide comments and attachments there.
78
+
You can see these requests on the **My Feedback** screen along with all your other **Problems** and **Suggestions**.
108
79
109
80
## Search for solutions or provide feedback
110
81
111
82
If you don't want to or can't use Visual Studio to report a problem, there's a chance the problem has already been reported and a solution posted on the [Visual Studio Developer Community](https://developercommunity.visualstudio.com/) page.
112
83
113
-
If you don't have a problem to report but want to suggest a feature, there's a place for that, too. For more information, see the [Suggest a feature](https://developercommunity.visualstudio.com/content/idea/post.html?space=8) page.
84
+
If you don't have a problem to report but want to suggest a feature, there's a place for doing that too. For more information, see the [Suggest a feature](https://developercommunity.visualstudio.com/content/idea/post.html?space=8) page.
114
85
115
86
## See also
116
87
88
+
*[Developer Community Guidelines](https://docs.microsoft.com/visualstudio/ide/developer-community-guidelines)
117
89
*[Visual Studio feedback options](../ide/feedback-options.md)
118
90
*[Report a problem with Visual Studio for Mac](/visualstudio/mac/report-a-problem)
119
91
*[Report a problem with C++](/cpp/how-to-report-a-problem-with-the-visual-cpp-toolset)
Copy file name to clipboardExpand all lines: docs/ide/report-a-problem.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ After you report a problem, states indicate where your submissions are in their
46
46
47
47
48
48
49
-
**Need More Info** indicates that we need more diagnostic information from you so that we can go forward with the investigation. [Learn how to respond to Need More Info requests.](./how-to-report-a-problem-with-visual-studio.md#when-further-information-is-needed-need-more-info)
49
+
**Need More Info** indicates that we need more diagnostic information from you so that we can go forward with the investigation. [Learn how to respond to Need More Info requests.](./how-to-report-a-problem-with-visual-studio.md#when-further-information-is-needed)
0 commit comments