Discussion: The GitHub Issue Tracker for the aspnet/Tooling repo is now deprecated in favor of the Report a Problem tool

[webtools-bot]

This is the discussion thread for deprecation of GitHub Issue Tracker for the aspnet/Tooling repo - please post your questions and feedback here!

To report new issues, use the Report a Problem tool. The GitHub Issue Tracker for the aspnet/Tooling repo is now deprecated in favor of the Report a Problem tool.

If you encounter a problem with Visual Studio, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio’s Talk to Us page for more details.

Here is the deprecation plan:
• Starting Mar 27 2017, any new issues opened in this repo will be automatically closed.
• In a phased manner, a message will be posted to individual issues about the issue tracker deprecation. Four weeks after the message is posted, the issue will be automatically closed.

[NickCraver]

Why is the assumption that every issue is a problem? Many of these are feature requests, the tooling inside Visual Studio being called "Report a Problem" is inherently off-putting and incorrect for a place to ask for features. As a user, where are we supposed to ask for features?

We came here after User Voice for Visual Studio because tracking wasn't a thing there at all. You never got any updates or real discussion. Being moved yet again to a tool where the description doesn't even work is not a welcoming change.

Note that "Provide a suggestion" inside Visual Studio still goes to User Voice. We're going in circles here, can we please stop moving the cheese and losing all the discussion each time we do it?

[renatoeufe]

Please stop wasting time on stupid ideas. No offense.

[Bartmax]

What to do if visual studio Report a Problem feature does not work? Because, you know, it doesn't always work ;)

I understand that the "report tool" gives you more info, but sometimes there's no more info to share, you don't need my dump to read this.

Tooling repo was amazing, in line with other feedback and also github was done better.

A better option would be to make the report a problem create a github issue on this repo.
Thing is, when someone has a problem and it's public, people can then check and see if it was fixed, if there's a workaround, etc.
Right now the "report a problem" kept everything in the dark of, you know, a web search... 👎

[PureKrome]

Maybe ... have the ability for people in VS to

• click button to show a list of relevant info/stats which MS would like/need
• copy/pasta. 🍝
• paste into the GH issue.

and .. we (the community) can continue to see all of the problems that are occurring AND can possibly help OR find a related problem-with-an-answer and move on...

EDIT/UPDATE: Lol. so @webtools-bot is a BOT .. and will 'get this GH issue-comment' .. and well .. it's a bot => /dev/null :( Q.E.D 😢

[damianh]

What about people that don't use VS?

[mlorbetske]

Looping myself in and tagging a few others to make sure that notifications for this thread get surfaced.

@barrytang @balachir @Andrew-MSFT

[shana]

Having users send data into a black box is not the way you build a community, no matter how nice that box is on the receiving end.

[Jetski5822]

Why move from a tool the community enjoy using, to a black box internal tool! It makes zero sense.

We would rather you deprecated that other tool and moved here.

[AndrewBrianHall]

We appreciate your feedback and input on this. Our apologies at the speed at which we moved without first opening the conversation up here, so we’d like to pause and do that now.

The planned change arose from the fact that the Visual Studio organization is moving to using the Developer Community as the centralized source for tracking and interacting on incoming issues for the Visual Studio product itself. From a team perspective, we obviously need to respond to and interact with customers using the Developer Community portal, additionally it naturally flows into our internal issue tracking system that is associated with our source code. We recognize that ASP.NET and .NET tooling blur the lines in some ways because in many cases the source code lives in GitHub which makes it natural to track issues and have discussions in the same location as the source. However, in the case of our team, this particular repo does not contain any source, which decouples it from the standard workflow of the team.

As such we are proposing the following for this repo:

• New issue tracking for ASP.NET tools in Visual Studio will move to Visual Studio’s Developer Community. This is an open system that enables the Visual Studio team to interact with the issue filer, is searchable, and supports collecting important information about the product with just a few clicks, as well as flowing into our internal issue tracking system that is easily transferrable among teams. We will also provide clear routing guidance for where to file issues in open source parts of the products such as the .NET CLI, the .NET Project system, Visual Studio Code, etc.
• This repo will remain an open platform for discussing important design and feature requests.
• To better indicate the purpose of this repository, we will rename it to aspnet/tooling-discussions

Please let us know your thoughts/feedback on this direction.