Azure DevOps Integration - Epics Field Mappings

This article explains the Azure DevOps Epics to OnePlan Plans default field mappings for your integration.

To complete the Azure DevOps integration setup, you must complete:

1. Azure DevOps Integration - OnePlan Setup

2. Azure DevOps Integration - Azure DevOps Setup

3. (You are here) Azure DevOps Integration - Epics Field Mappings

The following video walks through the default field mappings for the Azure DevOps and OnePlan Epics integration.

Important

After the integration is installed, it is best practice to check the default field mappings for errors or missing mappings.

Integration information

Functionality

This integration has three main use cases for functionality.

1. Create or Update Plans from OnePlan as Epics in Azure DevOps.

2. Create or Update work items under the Epics in Azure DevOps into OnePlan WorkPlan Tasks (Backlog work type).

3. Create or Update sprints from Azure DevOps into OnePlan.

NOTE: The backlog item sync is bi-directional even after the initial sync. You can create or edit data in OnePlan or Azure DevOps and then sync to the other system. The only fields that are not editable in OnePlan are the ones you choose to only sync from DevOps to OnePlan.

Scheduled jobs

The following scheduled jobs are installed by default.

1. SynchTeamProjects

   • Synchronize all team projects (including sub team projects) into a default choice fields in OnePlan (Team Projects Areas).

2. OnePlanUpdate

   • Synchronize Epics from Azure DevOps as Plans in OnePlan, and its WorkItems beneath the Epics as WorkPlan Tasks of Backlog Work Type.

   • Work item types synchronized are based on the ones specified at the Azure DevOps configurations steps above in OneConnect.

3. OnePlanPublish

   • Synchronize OnePlan plans as Epics in Azure DevOps.

Default field created

The following field is created in OnePlan at the time of setting up the integration: Team Projects Areas

• This field is auto created during integration installation at the Plan level in OnePlan.

• This field is a choice text field.

• This field will be used to indicate which Azure DevOps Team Projects a plan should get created in Azure DevOps.

• This field will be auto populated when SynchTeamProjects schedule job is running.

Default field mappings

Plans (OnePlan) <--> Epics (Azure DevOps)

OnePlan Fields	Azure Dev Ops Fields	Direction	Notes
Name	Title	Both	Required
Team Projects Areas	Area ID	Both	Required (Important)
Owner	Assigned To	Both	Required
Portfolio Plan Type	Work Item Type	Azure DevOps to OnePlan	Required

Backlogs (OnePlan) <--> Items (Azure DevOps)

OnePlan Fields	Azure DevOps Fields	Direction	Notes
Name	Title	Both	Required
Parent ID (Structure)	Parent Item ID	Azure DevOps to OnePlan	Required (Important)
Assigned To	Assigned To	Azure DevOps to OnePlan	Required
Portfolio Plan Type	Work Item Type	Azure DevOps to OnePlan	Required
Start	Iteration Start Date	Azure DevOps to OnePlan	Optional
End	Iteration Finish Date	Azure DevOps to OnePlan	Optional
Iteration (OnePlan System)	Iteration Path	Azure DevOps to OnePlan	Required for Sprint
Status	State	Azure DevOps to OnePlan	Optional
Effort	Original Estimate	Azure DevOps to OnePlan	Optional
Remaining Effort	Remaining Work	OnePlan to Azure DevOps	Optional

Lookup Tables (OnePlan) <--> Team Area Projects (Azure DevOps)

OnePlan Fields	Azure Dev Ops Fields	Direction	Notes
Team Projects Areas (Plan)	Project/Area Name	Azure DevOps to OnePlan	Required (Important)

Additional mappings for existing users (before 01 October 2021)

To use the Sprints feature of the OnePlan and Azure DevOps integration, users who were using the integration before the 01 October 2021 need to update mappings to the following:

NOTE: This mapping will allow work items that are synchronized as backlog items in OnePlan be referenced to its corresponding sprint. This setting is be needed for new users (after 01 October 2021) as it will be mapped by default.

Additional Notes

1. Start Date and Finish Date at the Backlogs and Items mapping level are based on the iteration start and finish date in Azure DevOps.

2. Task and Bug need to be in an iteration in order for them to synch into OnePlan.

3. Plans that are synchronized into Azure DevOps need to have a valid Team Projects Areas field filled with value.