does changing ms project mapping file affect tfs

Status synchronization: As team members add or modify work items that are set to Submit to Project Server, the synchronization engine automatically submits updates to the status queue. For more information, see Updates to Fields that Contain Hours later in this topic. Mirror fields are read-only.īy default, the OnConflict attribute is unspecified for the Remaining Work and Completed Work fields, which allows the mapped fields to differ between Team Foundation Server and Project Server. However, when a task is published to Project Server for the first time, both the reference field and the mirror field are set, regardless of the value to which the OnConflict attribute was assigned. The synchronization engine always updates the mirror field but updates the reference field only when the OnConflict attribute is set to PSWin. Only fields that are mapped from Project Server to Team Foundation Server ( targetToTfs mapping) are updated in this step.

Team Foundation synchronization: The synchronization engine automatically detects additions and changes that were published to Project Server and pulls those updates into Team Foundation Server. Also, you cannot change a task to a different type of work item after it has been published to or submitted from Team Foundation Server. You cannot modify the Publish to Team Project value that is assigned to a task, and you cannot change the Submit to Project Server field in Team Foundation. When a work item or task has been scheduled to participate in synchronization, you cannot remove it from synchronization except by deleting the task from the project plan. The following table provides additional notes about the synchronization process and how fields are updated during each step of the process. Overview of the Update Field ProcessĪs the following illustration shows, data moves from Project Server, to Team Foundation Server, to the status queue in an instance of PWA, to the enterprise project plan, and finally back to Project Server. If the plan was not published, nested child work items cannot flow into the approval queue. Tasks will not update correctly if the project manager rejects one or more submission updates or if the project plan was not published.

The data type of the affected field or fields, the OnConflict field mapping attribute, and task hierarchy affect how the synchronization engine updates specific fields. You should review this topic if one or more fields are not synchronizing as you expect between Visual Studio Team Foundation Server and Microsoft Project Server. 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.

Does changing ms project mapping file affect tfs