Geeks With Blogs
Mike Azocar So long and thanks for all the Fish!

I posted recently on how you make a field on a work item read-only. The example that I used for this post was the Estimate field. When I set up the current project in VSTS (we are using the CMMI process template) a few months ago, I was not able to get the Estimate field to match the Baseline created in my project plan. I assumed that the estimate field was not mapped correctly and had decided that I would post on how to map this. What I found is that the Baseline field is in fact mapped to a field named "Microsoft.VSTS.Scheduling.BaselineWork." So getting the Estimate field to match the baseline in the project plan is easy.

á

Here's what I did:

  1. I used witexport to download the Task (see my previous post titled "Making VSTS Work Items Editable" for more info on how to do most of these steps.)
  2. In the "FORM" section I found the "Group" labeled "Schedule."
  3. I located the "Control" element for Estimate.
  4. I changed the value of the "FieldName" attribute to "Microsoft.VSTS.Scheduling.BaselineWork" and I also added the attribute "ReadOnly" with a value of "True" because I still don't want any changes to this value.
  5. I used witimport to reload the Task.

á

Here is my project plan:

á

Here is what I ended up with in VSTS:

á

Now when I baseline my project the result will show as the estimate for my developers to view.

á

Happy Coding!

á

Posted on Friday, May 26, 2006 1:05 PM Administration | Back to top


Comments on this post: The Estimate Field in VSTS, it’s not your father’s Baseline

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Mike Azocar | Powered by: GeeksWithBlogs.net