Unless I'm missing something, a VCS Root setup on a template cannot change the checkout rules per configuration instance that uses the template.
I want each configuration to use a shared VCS Root and edit the checkout rules to a branch specific to that configuration. Is it possible to set a property value when the instance is created from the template and use that property value in a checkout rule of VCS Root set in the template? In that way, the template could have the VCS Root and apply the property dynamically in the configuration instances.
Being able to do this would eliminate a number of steps in creating a new configuration from a template. This is a common need when working with branches. Currently, we use SVN. Perhaps it is different if using Git (which we are moving to)?