Thanks guys. Those are the steps I was hoping to avoid. I performed them this morning and sure enough, it is all working. It took over two hours. I recommend not using the new bulk work item update from the Web Access. It was horrendously slow. I had to cancel it and use Excel. I started with Excel first, but it can't populate long Steps to Reproduce, so I modified the work item type to perform a copy, and just updated the history of all the Bugs.
I must say though, what is the point of the bugfieldmapping if it is hard-coded? It is quite disappointing the apparent disregard for existing installs. Now on to update all our reports against the new cube :S Regards Matthew Rowan On Fri, Jun 11, 2010 at 10:59 PM, Ed Blankenship <e...@notionsolutions.com>wrote: > Hi Matthew, > > > > You do indeed need to have fields with the reference names that Microsoft > Test Manager is looking for if you want the fields to be populated. When I > have upgraded team projects using MSF CMMI v4.2 to MSF CMMI v5.0, I have > gone through these steps: > > > > · create a new HTML field on the Bug WIT called > Microsoft.VSTS.TCM.ReproSteps > > · copy the contents of the Microsoft.VSTS.CMMI.StepsToReproducefield > to the new field > > · remove the old field: Microsoft.VSTS.CMMI.StepsToReproduce > > > > There isn’t a way to customize Microsoft Test Manager to use fields other > than the ones they were expecting. They are hard-coded values. L > > > > Take care, > > > > *Ed Blankenship** > *Notion Solutions, Inc. <http://www.notionsolutions.com/>, an > Imaginet<http://www.imaginets.com/>Company > Microsoft MVP (TFS, Visual Studio ALM, and Team System) > Blog <http://www.edsquared.com/> | Microsoft > MVP<https://mvp.support.microsoft.com/profile/ed.blankenship>| > E-Mail <e...@notionsolutions.com?subject=your%20e-mail> | > Skype<callto://EdBlankenship/>| > Twitter <http://www.twitter.com/edblankenship> | > LinkedIn<http://www.linkedin.com/in/edblankenship>| Voice/SMS: 214-810-6733 > > > > *From:* oztfs-boun...@oztfs.com [mailto:oztfs-boun...@oztfs.com] *On > Behalf Of *Jon Harald Berge > *Sent:* Friday, June 11, 2010 1:52 AM > *To:* ozTFS > *Subject:* RE: Test Runner not populating bug report > > > > Hi, > > > > I don’t know about the fields, but Lab Management is not needed to get the > system information. However you need to check the System Information > checkbox in the Test Settings->Data and Diagnostics for your test plan. It > is checked by default. > > > > Regards, > > Jon Harald Berge > > > > > > *From:* oztfs-boun...@oztfs.com [mailto:oztfs-boun...@oztfs.com] *On > Behalf Of *Matthew Rowan > *Sent:* 11. juni 2010 06:58 > *To:* oztfs@oztfs.com > *Subject:* Test Runner not populating bug report > > > > Hi > > > > I've just completed the upgrade from TFS 2008 to TFS 2010 this week. I've > added Test Case Management support following the steps > here<http://msdn.microsoft.com/en-us/library/ff452591(v=VS.100).aspx>. > One difference is that I did not add Microsoft.VSTS.TCM.ReproSteps field > instead, in the ReproSteps of the bugfieldmapping I added our existing > Microsoft.VSTS.CMMI.StepsToReproduce field. > > > > Using the Test Runner to create a bug, no repro steps are entered, and the > System Info field displays "Value cannot be null. Parameter name: name". Is > there something special with the TCM.ReproSteps field, that I can't reuse an > existing field of the same type? Do I need to run with Lab Management before > I get System Info? Or is there something I'm missing? > > > > Cheers > > > > Matthew Rowan > > _______________________________________________ > oztfs mailing list > oztfs@oztfs.com > http://prdlxvm0001.codify.net/mailman/listinfo/oztfs > >
_______________________________________________ oztfs mailing list oztfs@oztfs.com http://prdlxvm0001.codify.net/mailman/listinfo/oztfs
