Azure DevOps Epics Integration - Default Field Mappings and Scheduled Jobs – Support

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

Default Field Mappings

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

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

Plans - Epics

OnePlan Fields	Azure DevOps Fields	Direction	Notes
Name	Title	Both	Required
Team Project Areas	Area ID	Both	Required
Owner	Assigned To	Both	Required
Portfolio Plan Type	Work Plan Type	ADO to OnePlan	Recommended

Backlog - Items

OnePlan Fields	Azure DevOps Fields	Direction	Notes
Name	Title	Both	Required
Plan Id (Structure)	Parent Item ID	Both	Recommended
Assigned To	Assigned To	Both
Iteration (OnePlan)	Iteration Path	Both	Recommended
Item Type	Work Item Type	Both	Recommended
Start	Iteration Start Date	ADO to OnePlan
Due	Iteration End Date	ADO to OnePlan
Effort	Original Estimate	ADO to OnePlan
Points	Story Points	ADO to OnePlan
Remaining Effort	Remaining Work	OnePlan to ADO

Lookup Tables - Team Area Projects

OnePlan Fields	Azure DevOps Fields	Direction	Notes
Team Project Areas (Plan)	Project/Area Name	ADO to OnePlan	Recommended

Lookup Tables - Pick List Lookup

This table is intentionally left empty. Only choice fields should be mapped in this table to run the SyncLookupToADO strategy.

OnePlan Fields	Azure DevOps Fields	Direction	Notes

The following scheduled jobs are installed by default:

OnePlan Update: Publish data from Azure DevOps to OnePlan.

This strategy has a filter within the Azure DevOps - OnePlan > Epics – Plans section. This filter will only sync items that are already mapped to OnePlan. Please talk to your OnePlan Contact about filtering the information being brought in from Azure DevOps. If this filter is removed (and not replaced with an alternative filter), all items will be brought into OnePlan.
OnePlan Publish: Publish data from OnePlan to Azure DevOps.

This strategy has a filter within the OnePlan - Azure DevOps > Plans – Epics section. This filter will only sync items that are already mapped to OnePlan. Please talk to your OnePlan Contact about filtering the information being brought into Azure DevOps. If this filter is removed (and not replaced with an alternative filter), all items will be brought into Azure DevOps.

These strategies are available to be scheduled but are not installed by default. Click on the Add Schedule button to see the list of strategies.

OnePlanPlanItemsCleanUp: Deletes OnePlan task/backlog items that have been deleted from Azure DevOps. This does not delete plans from OnePlan.
SyncLookupToADO: Synchronize a list of items from Oneplan to ADO lookup field.