Welcome to MSDN Blogs Sign in | Join | Help

Bug handling on Connect & Transparency

I've blogged a fair about over the past couple of years on transparency in our process.  I've also advocated for it a great deal internally.  This post caught my eye today both because it is a great commentary on transparency and a great description of how we handle bugs that customers enter throught the http://connect.microsoft.com site.  All too often I see the other side of it where a customer is upset because we rejected a bug and didn't provide any reasonable feedback as to why.  We continue to work on making sure everyone in the division who deals with customer bugs is properly educated on how to deal with them effectively and respectfully.

Here's the post: http://blogs.conchango.com/jamiethomson/archive/2007/10/25/Commendable-transparency-from-the-Visual-Studio-team.aspx

Brian

Published Monday, October 29, 2007 8:33 AM by bharry

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# re: Bug handling on Connect & Transparency

Monday, October 29, 2007 4:40 PM by GertGregers

I have myself experienced a feedback being closed as duplicate on connect, and I was not able to find the original post leaving me with no clue on how to procede. This was an extremely frustating experience, and the chances that I'll give additional feedback on connect is now very slim.

# re: Bug handling on Connect & Transparency

Monday, October 29, 2007 5:06 PM by bharry

I'm sorry that was a bad experience for you.  What this usually means is that someone internally found the same issue already and it was resolved as a duplicate of that bug.  Unfortunately, the integration between Connect and our internal TFS work item tracking database is not terribly good.  The result is that you don't see the linked bug.  We tell people, when they are resolving a connect bug to write a customer visible comment that explains this kind of situation and what the ultimate resolution is but sometimes they don't notice it's a Connect bug.

I hope you'll give it another try at some point and have a better experience.

Brian

# Connect でのバグ処理と透明性

Tuesday, May 20, 2008 12:46 AM by bharry's WebLog

この 2 ~ 3 年、私はかなり頻繁にブログで自分のチームの透明性について書いてきました。社内でも積極的に透明性の重要性を主張しています。今日紹介するブログに注目したのは、透明性に関する優れた見解が述べられており、ユーザーから

Leave a Comment

(required) 
required 
(required) 
 
Page view tracker