Required fields,workflows and form layout for Change Request work items in VSTS 2010 beta1

Question

Hi Can anyone give me a sample of creating a new Change Request work item type in MSF Agile v5.0 template? Which fields and work flows are required for a CR? I am asking because there are no CRs existing in our process template and I would like to customize it.

Answer 1

You can easily create a CR by reusing the one from MSF for CMMI process improvement. Use the import tools available and import the CR work item type into the MSF Agile-based team project, or edit the template and upload a modified version. The documentation on how to customize a MSF process template explains how to do that.

Answer 2

Thanks Clementino. Sorry for the very late response. I eventually did the same and things were working fine, till now  when I get an error saying "InvalidNotEmpty" for the 'Assigned To' field, when editing and saving an existing CR from any state to the "Closed" state. This is through my application using TFS API 2010 Beta 2.

When I tried using Team Explorer, I find that the 'Assigned To' field goes blank and is disabled when a CR goes to the Closed state. When I purposely did the same with my application, it saves successfully.

My question is: Why should the 'Assigned To' field become null?? Aren't we supposed to keep track of the work items in all their states? Or is there a problem with the WIT xml file?