CODEWITHSUNDEEP
tfs
user2974732
user2974732

Reputation: 103

Difference between TFS 2012 and TFS 2013 process templates

We are planning to upgrade from Tfs 2012 to Tfs 2013. Can anyone help me understand the difference in process templates between them? We use all three process templates for different projects.

Upvotes: 3

Views: 1503

Answers (2)

JohnH
JohnH

Reputation: 2133

TFS 2013 did not work well with our existing workspaces defined on remote network drives. TFS 2012 did work with this configuration.

After working several hours with our System Administrators, we gave up on trying to get the trying to get the existing network drive workspaces to work with the TFS 2013. Converting the workspaces to local drive locations enabled us to work with TFS 2013.

Upvotes: 0

jessehouwing
jessehouwing

Reputation: 114731

The changes are very minor, except for:

  • The introduction of Portfolio backlogs.
  • Test Plans and test Suites are now Work Item Types (TFS 2013 update 3).
  • The AgileConfig and CommonProcessConfig files have been merged to a single file inside the template

The minor changes:

  • Git support for the Source Control options
  • Stackrank type fields are now hidden by default (because Agile task boards are now features of the Standard CAL).
  • Tag field support through the API.

The easiest way to visualize all differences is by comparing them through the TFS Team Project Manager which can be downloaded here.

Upvotes: 6

Related Questions