<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>My experience on Connect Feedbacks</title><link>http://blogs.msdn.com/vsdata/archive/2009/06/09/my-experience-on-connect-feedbacks.aspx</link><description>Recently I have been working with some Visual Studio feedbacks reported through Microsoft Connect . I found that some feedbacks may contain multiple unrelated issues. On the other hand, one issue may be reported several times by the same person in different</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: My experience on Connect Feedbacks</title><link>http://blogs.msdn.com/vsdata/archive/2009/06/09/my-experience-on-connect-feedbacks.aspx#9711724</link><pubDate>Tue, 09 Jun 2009 05:40:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9711724</guid><dc:creator>Forrest</dc:creator><description>&lt;p&gt;Looks like the Connect Feedback doesn't contain comments on MSDN document.&lt;/p&gt;</description></item><item><title>re: My experience on Connect Feedbacks</title><link>http://blogs.msdn.com/vsdata/archive/2009/06/09/my-experience-on-connect-feedbacks.aspx#9725175</link><pubDate>Thu, 11 Jun 2009 01:32:54 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9725175</guid><dc:creator>SeeR</dc:creator><description>&lt;p&gt;Let me guess. You closed feedbacks with info like this: &amp;quot;We will investigate this feature in later version. Now it's to late&amp;quot; and they will be completly abandoned.&lt;/p&gt;
&lt;p&gt;That's just my impression of how MS is handling feedbacks. See example: &lt;a rel="nofollow" target="_new" href="http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=90732"&gt;http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=90732&lt;/a&gt;&lt;/p&gt;</description></item><item><title>re: My experience on Connect Feedbacks</title><link>http://blogs.msdn.com/vsdata/archive/2009/06/09/my-experience-on-connect-feedbacks.aspx#9810023</link><pubDate>Tue, 30 Jun 2009 23:49:59 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9810023</guid><dc:creator>commongenius</dc:creator><description>&lt;p&gt;I have seen a lot of comments from Microsoft employees saying &amp;quot;I am closing this issue but feel free to reactivate it if you have more information.&amp;quot; However, you should be aware that the Connect website changed fairly recently so that &amp;quot;Closed&amp;quot; issues cannot be reactivated by the user that reported them. The only option is to create a new ticket. It seems that the Connect website team made this change without notifying any of the teams that use the site, because I still very often see those kinds of comments. Imagine how frustrating it is for users to not only have their reported bug or suggestion be closed outright with little or no discussion, but then to be told to do something that they can't do!&lt;/p&gt;
</description></item><item><title>re: My experience on Connect Feedbacks</title><link>http://blogs.msdn.com/vsdata/archive/2009/06/09/my-experience-on-connect-feedbacks.aspx#9810271</link><pubDate>Wed, 01 Jul 2009 05:53:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9810271</guid><dc:creator>Yang Cao</dc:creator><description>&lt;p&gt;I understand your concern.&lt;/p&gt;
&lt;p&gt;First is that product team will try their best to reproduce the issue and sometimes due to complex configuration of user's environment, it's hard for product team to reproduce, thus cannot investigate not to mention fix the issue.&lt;/p&gt;
&lt;p&gt;If product team still fails to do anything about the issue, the bug will be closed. You're right that currently user cannot reactivate the bug. However there's a team keeping an eye on all the comments, so if a user could provide more information (might not be the original creator of the bug) in the comment, the team will help reactivate the bug and assign it to the right product team.&lt;/p&gt;
&lt;p&gt;Oh, and the connect team is considering adding the feature to enable user directly reactivate a bug.&lt;/p&gt;</description></item><item><title>re: My experience on Connect Feedbacks</title><link>http://blogs.msdn.com/vsdata/archive/2009/06/09/my-experience-on-connect-feedbacks.aspx#9842039</link><pubDate>Mon, 20 Jul 2009 21:27:32 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9842039</guid><dc:creator>John Chen</dc:creator><description>&lt;p&gt;Good news: The re-activations scenario in Connect Visual Studio has already been enabled recently. &lt;/p&gt;</description></item></channel></rss>