Allow for updating process templates on existing projects in TFS
To keep up with improving processes, there needs to be a migration path for existing templates to be upgraded to new templates. Some information in work items may be lost when mapping these to new work item types of the new templates, but this may well worth the benefits of moving to a newer process. Creating a new team project is not always feasible, especially if the source code versioning needs to be in place.
In Team Foundation Service (which is really great!!) it should be possible to edit the WIT's as it is possible with "classic" TFS. In our team we did some specific modifications that are important for our process - we'd like to see this also in TF Service.
I am aware that some teams are using SCRUM (I am a certified SCRUM Master), but some other teams (the stubborn kind) are using their own methodology and states.
I have the following suggestions, regarding the TFS project templates:
1. We should be able to upload a modified TFS project template to the TFS service.
2. That template should be visible only to the team that uploaded it, unless the team decides to share it to the world.
3. When creating the TFS project, we should be able to choose that TFS template
4. We should be able to export an existing TFS template to a specified name, if it got modified after the project got created
uprading existing team project to newer process template is not officially supported and requires a lot of manual steps.
Shawn Anderson commented
I agree with this one. I am betting the biggest issue is with the "states" due to highly structured there are, but a simple mapping between "old" and "new" and then allowing the upgrade to happen without triggering the automated process flow might be an easy and clean solution. If you think about it, this is not a regular occurrence, so a one time "skip" of notifications and constraint enforcement would be very acceptable.
This is one of the many reasons I don't invest in TFBuild. Only newbee build guys use it.
I've just set myself up and was getting quite excited then fell at the first hurdle - i.e. using our wit's....
The out of the box templates are just not enough for a serious project to use. When will this functionality be available?
Ed Biggs commented
It would be helpful to know if all/any part of this is now available? Something as small as adding a new field would help me massively.
Ivan Pavlović (MVP for Visual C#) commented
It would be great to enable simple updating of project templates for multiple projects. Enabling users to update process templates using witadmin would be even better
Ricardo Farinha commented
When will this functionality be available?
This is Malu from Bangalore, India. I have 2 question right now related to modify / update the existing template in TFS 2012.
a) Can we modify the existing template as per our requirement? If yes means up to what level? Please share point wise.
b) Is it possible to access our TFS collection by external user those who don't have access rights in our TFS Collection in our machine?
Thanks in advance. I am expecting reply.
Nicolae Carabut commented
Hit the same problem what should I do ?
I really appreciate TFS Service and the value it brings. We really, really need the ability to customize WIT items to better adapt to our development flow.
Still encountering the TF237113: You don't have enough permissions to complete the import operation.
I'm afraid without this ability, TFS Service is a no go for us.
R Philip Rogers commented
I was able to migrate one of our Agile 4.0 projects to Scrum 2.0 by following the steps in this blog by Martin Hinshelwood.
Jonathon Stevens commented
i'm confused as to why this still is here, this already happens in 2012?
When trying to import a custom WIT definition to an existing TFS project i get the error:
TF237113: You don't have enough permissions to complete the import operation.
(I read that this still isn't possible? source: http://social.msdn.microsoft.com/Forums/en-US/TFService/thread/fef6afd3-2093-4026-bdea-f502b1aa4d43)
Any updates on this since i really need to update the WIT for a scrum template based project
Charles Sterling commented
Please look at the 2012 RC...Much of this was added and the team would like to verity the implementation is working for people.
Manish Jain commented
Thank you for posting this idea. TFS/ALM team - considering # of people/team suffering from lack of this feature, it should be considered for vNext. This is something basic and should be priority over any new features.
Visual Studio ALM Team commented
Thanks guys. We hear this one a lot and it's definitely something we're considering. That said, we're not planning a full "migration" tool in vNext.
Folks -- I've merged the ideas. First time doing it, so hopefully I did it right. :-)
-Siddharth (Program Manager on TFS)
Deepak Chitnis commented
Daniel is right. Sorry, did not see it earlier before posting. However, the extra explaination could be helpful to understand the issue. Is there a way to merge these 2 ideas?
Daniel Steiner commented
same idea as this here "support upgrading to newer process template version for existing team projects"
Daniel Steiner commented
why have the original author of this idea been overriden by VS ALM Team ?
replacing the original author also prevents update notification of this idea. I don't think that there're some real technical reason to replace the author when the visualstudioalm customer feedback had been merged into visualstudio customer feedback