Is there any way to get TFS to create a seperate work item for each build error and or warning I hate having to trrack back the bug to the build report then magically I close one work item and all the errors in that build are fixed I would like to be more granular.

That blog looks very interesting and my solve my problems but, perhaps my TFS isn't working right

When I do a TFS build and the build has errors or warnings I get one single work item, all that is contained in that work item is some basic information about the build and a link to the build log which lists the errors.

What I want is a work item or bug item to be generated for each error and or warning that occurs during the build. So if there were 4 build errors there would be 4 work items, if there were 10 warnings 10 work items. Each item would contain a single error or warning. Is it not supposed to work that way

Your question is very interesting. Let me tell my suggestion on this regard.

The build workitem creation is especially for the particular build which is failed due to COMPILATION errors [higher priority - since it won't go to next phase like unit test or code analysis and it will create a new workitem called BUG and assigned to Administrator] or Unit Tests or Code analysis ..

So from the above term, if the build failed means it will create one workitem called BUG and automatically it will be assigned to Administrator......

You can't create multiple workitems for the corresponding errors..or even you can consider of this case..if unit test failure and code analysis failure means ...there will be one workitem only.....

Also they have provided one more facility like Associated CHANGESETS...with the corresponding builds....let's check out that..so that you can get to know which checkin or code affects the builds...

then the workflow will go like this...Administrator will assign the faliure workitem to TRIAGE http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=1009121&SiteID=1 team and this team will investigate about the failure and if it is approved means it will go to corresponding developer to fix it..and will be closed once testing is done and passed QA...

Thanks,
Kathir