User Tools

Site Tools


Sidebar

integration_hub:integrations:online_vsts

Online <> VSTS

Project Server Online and Visual Studio Team Services Integration

In this article

  • How to start using the Integration Hub
  • Basic info about Sync between VSTS and Project Online
  • Details of VSTS and Project Online integration
  • Notes and Limitations

How to start using the Integration Hub

Step 1: Install "Integration Hub" App from Visual Studio Marketplace on your tenant

:!: Note: The Visual Studio extension is not required for using Integration Hub. You also can install SharePoint app and use it to open your Integration Hub site.

You can use Project Online or VSTS to get to Integration Hub.
Please note, we recommend you to install VSTS app, since it provides you some more information about current state of integration.

Step 2: Configure environment to work with Integration Hub

Go through the provided steps to setup required settings in your environment to work with Integration Hub.

Step 3: Use it

In case you have any questions, contact us at support@fluentpro.com or via live chat by clicking the appropriate icon on the Integration Hub site

< Back to Top

Basic info about Sync between VSTS and Project Online

Synchronization between Project Online (Online) and Visual Studio Team Services (VSTS)

System supports the data transformation rules where you can implement your business rules. It is extensible and configurable, different business rules can be implemented for your needs.

An application allows to migrate data in both directions - from Project Online to Visual Studio Team Services and vice versa. For cooperation between these two systems and correct data migration some settings should be pre-defined. See “Step 2” above.

Data will be migrated from Project Online to Visual Studio Team Services in case when:

  • “VSTS Project” custom fields is pre-populated with appropriate project name and this one has already been created in Visual Studio Team Services.
  • In Project Online “Sync To VSTS” flag should be set to “Yes” for the item that should be synchronized.
  • Data will be migrated if task marked as sync = yes and names of the projects in Online and in VSTS are the same.

Data will be migrated from Visual Studio Team System to Project Online in case when:

  • “Sync To PO” flag is set to “YES”.
  • Data will be migrated if task marked as sync = yes and appropriate VSTS work item field contains exact name of the Online project.

< Back to Top

Details of VSTS and Project Online integration

Fields Mapping

ProjectServerOnline Meaning VSTS
Custom field: Project.“VSTS Project Field”System field: Project.Name
System field: Project.NameCustom field: WorkItem.“PO Project Name”
Custom field: Task.“Sync To VSTS” = Custom field: WorkItem.“Sync To PO”
Custom field: Task.”VSTS work item type” = System field: WorkItem.Type
System field: Task.Name = System field: WorkItem.Title
System field: Task.Work = System field: WorkItem.OriginalEstimate
System field: Task.ActualWork = System field: WorkItem.CompletedWork
System field: Task.RemainingWork = System field: WorkItem.RemainingWork
System field: Task.Assignment = System field: WorkItem.Assignment
System field: Task.ParentTaskId = System field: WorkItem.ParentTaskId

Integration

Integration Hub synchronization between Project Online (Online) and Visual Studio Team Services (VSTS) supports the following:

I. While synchronization tasks from Project Online to VSTS work items:

a) Task created in Online (Project Online is Origin system)

- Task Name;

- Work;

- Actual Work;

- Remaining Work;

- Assignments (One assignment in Online equals one separate Work Item in VSTS);

- VSTS Work Item Type (Bug, Task, Epic, Feature, Issue, Test Case, User Story);

- Hierarchy structure;

b) Work Item created in VSTS (VSTS is Origin system)

- Original Estimate;

- Completed Work;

- Remaining Work;

- Assignment;

- VSTS Work Item Type;

- Hierarchy structure;

II. While synchronization work items from VSTS to Project Online tasks:

a) Task created in Online (Project Online is Origin system)

- Original Estimate;

- Completed Work;

- Remaining Work;

- Assignment;

- VSTS Work Item Type;

- Hierarchy structure (Only while first sync, updates are not supported);

b) Work Item created in VSTS (VSTS is Origin system)

- Work Item Title;

- Original Estimate;

- Completed Work;

- Remaining Work;

- Assignment;

- VSTS Work Item Type;

- Hierarchy structure (Only while first sync, updates are not supported);

< Back to Top

Notes and Limitations

One project from Project Online is synced to one project from Visual Studio Team Services.

Data synchronisation can be launched manually or can be scheduled. An automatic rule for the synchronisation can be created and system will automatically kick off appropriate jobs and data transformation process.

System supports filtering rules which help to indicate a specific project you prefer to work with.

In case you are updating the work hours for a task or a work item, these changes will be updated on target/source after migration.

Notes:

  • Assignments matched by Emails. Resource assigned to Task in Project Online must be with the same Email as an Email of Visual Studio Team Services user account. The same requirement is actual in reverse case - Email of Visual Studio Team Services user account assigned to Work Item must be equal to Email of resource in Project Online.

  • For a huge integration, where execution time approximately equals 1 hour or items quantity is about 500, use VSTS connection with Personal Access Token instead of OAuth authorization. Personal Access Token (PAT) can be generated in VSTS → Security → Personal access tokens.

  • Do not unassign resources from manual scheduled tasks where “Sync To VSTS” = Yes, since this will cause loss of task work progress in Online.

  • Do not assign same Resource on Siblings in VSTS. Siblings are work items related to the same Task but related to the different Online Resource Assignments in Online .
    If you have T1a1 (Task1 with Assignment1) and T1a2, do not change a2 to a1 for second sibling task (eg: T1a1 & T1a1), since in Online T1 will be updated with data only from T1a1 and data from T1a1 will be overwritten and lost.

  • All work progress of task assignment in Online will be cleared and set to 0 on unassigning the work item in VSTS.

  • In case you have more than one assignment on same Task and unassign such task in Online, an appropriate VSTS sibling work item will be marked as “(Deleted)” text in Title and synchronization will be turned off.

  • You can not track working time in synchronizable Work Item which has child work items in VSTS. Time tracked in VSTS work item with child items will always be overwritten by values from Summary Task in Project Online.

  • Do not change authentication type of the connections in integration scenario. Create new connection instead.

  • Changes in hierarchy can only be synced from Project Online to VSTS. Hierarchy changes in VSTS will not be synced to Project Online.

  • Do not change work item type from “Test Case” to anything else in Project Online, since VSTS does not support it.

  • Do not change work item type from any type to “Issue” in Project Online, since VSTS does not support it because of Issue does not have states “New” and “Resolved”.

  • Deletion of the syncable entities is not supported for now.

  • Resource must exist on PWA to be automatically added to Project Team in case of assigning this resource to some synchronizable Task in Agile System (VSTS, Jira, etc…).

< Back to Top


integration_hub/integrations/online_vsts.txt · Last modified: 2018/01/23 15:46 by Anita Boiadzhian