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.
Unfortunately we have had to make the decision to not bring the new Inheritance model to TFS on-prem with the next major release. It was a tough decision that we didn’t take lightly. The scope cuts that we had to make in order to deliver it to on-prem were just too painful, and would not give the User Experience we would be proud of.
We are still planning to bring it to our on-prem customers in a future release of TFS.
Sorry for not having a better answer.
VSTS/TFS Program Manager
Adam Coulter commented
I believe this is coming in TFS 2019, and subsequent updates. Look for Brian Harry's comment on this here: https://blogs.msdn.microsoft.com/bharry/2018/02/28/vsts-and-tfs-roadmap-update/#div-comment-453975
Christopher Mank commented
@Jeff - This request is talking about bringing the inheritance model of process templates, that is only available in VSTS, down to TFS.
The article below indicates that the Configure Features wizard updates your team project process template, and that there are options if it fails. How is that different from this idea?
@Brian and @Jeroen. To be clear, we will not ship the new model to TFS 2018 (or whatever name we will give it). That version is internally known as Dev16. It is currently targeted to ship as part of Dev17.
Brian Auerbach commented
Ewald, please use version numbers when describing things like this. The last we heard was "next major version", which was prior to the release of TFS 2017. Now you're saying not in the "next "version", so 2021?
Jeroen Janssen commented
Do you mean TFS2017 with "next major release" here or is that already the version "after" 2017?
In other words, are we talking about waiting for at least two releases after TFS2017 before this could become reality?
Will this feature become available in an update for TFS2017 or for the next major version?
And does this mean that TFS2017 on-premises does not yet support shared and inherited processes like TFS Team Services does?
Michael L commented
If I use the new functionality, will TFSAggregator plugin still work?
Greg R commented
Could you please clarify the question from Brian, what is the next major version? tfs 2015.2 or TS2016 ?
@Brian, the next version of TFS Is the new major version of TFS
Hi Justin -- when you say the "next version of Team Foundation Server", I want to clarify what exactly you mean. Will this be in TFS 2015.2 or a new major version?
Need this now, so yes please.
Would love to see an update on this item? Any progress?
Greg R commented
Simple GUI option to identify Project Process Template Used
Currently an SQL script is needed on the server to be sure what template was used on a project.
This should be a simple bit of info displayed on the project by the web portal
I saw this has a need years ago, so from the beginning I have used a batch file (old school) that utilizes this command:
witadmin importwitd /f:"%SourceFolder%Task.xml" /collection:%TargetCollection% /p:%TargetProject%.
The command above applies the Task.xml WIT to a specific project.
I use the batch file to do the initial customization of a new project too,
Of course you have to do an analysis of your differences before applying a new template (if field values change, you might want the "AllowExistingValue" attribute on the field.
Lakshmi Reddy commented
I am using TFS 2010. I have 2 team projects under a collection, project 1 and project 2. By default we have six work item types under the process template. Now I added 2 more work items and updated process template. But I cannot see the new work items in project 1 and project 2. But I can see for the new projects. How can I get new work item types in existing projects.
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?