Deep Dive on Configure Features

This post details the internal workings of the TFS 2012 upgrade wizard, explaining how it validates process templates against team project artifacts. It outlines the three validation steps: checking for existence in the process template, mapping to existing artifacts, and ensuring no conflicts. It also describes message severities (warning, error, critical error) and how they affect the upgrade process. Specific examples are provided for handling customized process templates, including logic for mapping fields like 'Effort' to 'OriginalEstimate' when 'Size' is not present, and mapping states like 'Proposed' when a direct match doesn't exist in certain work item types.