The synchronization engine then maintains data between the new tasks and the work items from which they were created. You can then copy from the old tasks to the new tasks any information that Team Foundation Server does not store, and then delete the old tasks. Instead, you specify work items that you want to synchronize, and then the migration process automatically creates additional tasks that are based on those work items. The integration of Team Foundation Server and Microsoft Project Server does not support mapping the existing tasks in a project plan in Project Server to the work items to which they are bound in Team Foundation Server.
When you map a project plan that was previously bound to Team Foundation Server, you replace the tasks in your project plan with new tasks that the synchronization engine creates. For more information, see Operational differences in managing projects using TFS and Project. Before you perform this mapping, you should review the differences in how you manage projects based on these two methods.
You can then obtain the benefits of synchronization over those that the Team Foundation add-in to Microsoft Project Professional provides. You can map a project plan that you have been publishing to and refreshing from Visual Studio Team Foundation Server (TFS) to switch to synchronizing with TFS. If you upgrade to TFS 2017 or want to use a third party option, see Synchronize TFS with Project Server.
TFS 2017 and later versions no longer support native integration with Microsoft Project Server.
0 kommentar(er)
