This article explains the Azure DevOps Epics to OnePlan Plans default field mappings and scheduled jobs for your integration.
Integration Information
OnePlan Changes
Once the integration is complete, three things will occur in the OnePlan integration page:
- Integration Line-Item Creation.
- Integration Event Creation.
- An integration is established, signifying the successfully setup and activation of the synchronization process between OnePlan and Azure DevOps.
- Azure DevOps availability in Connected Systems.
- After completion, Azure DevOps becomes accessible within the Connected Systems icon, indicating its successful integration with OnePlan.
Integration Line-item Details
Each entry in the Integration section provides an overview of OneConnect Integrations associated with the OnePlan Work Plan, offering a comprehensive list of connected systems.
Integration Events and Data Synchronization
Integration events facilitate automated responses, allowing data transfer from OnePlan to Azure DevOps. When triggered, the OnePlanPublish strategy is activated for any item linked to Azure DevOps. This process ensures that mapped values from OnePlan are updated within Azure DevOps.
Triggers for Event Activation
- At the plan details page in OnePlan: This occurs after modification and automatic saving of an item.
- At the backlog section in OnePlan: This action is initiated after editing a field and clicking Save.
Identifying Connected Systems
Any item connected to Azure DevOps will display the Azure DevOps icon on both the My Portfolio page and the Work Plan Backlog page, indicating the association between plans/tasks and Azure DevOps.
Connecting Items
To link an item from OnePlan to Azure DevOps:
- Navigate to the Work Plan – Backlog page.
- Click on the plug icon (Connected Systems Icon).
- Select the option to connect to an existing item in Azure DevOps or create a new item.
- Once connected, the Connected Systems window allows for Import, Export, or Opening of the Azure DevOps plan-level item.
Important
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 |
|
Portfolio Plan Type |
Work Item Type |
ADO to OnePlan |
Recommended |
|
Owner |
Assigned To |
Both |
Required |
|
Team Project Areas |
Area ID |
Both |
Required |
Backlog - Items
|
OnePlan Fields |
Azure DevOps Fields |
Direction |
Notes |
|---|---|---|---|
|
Assigned To |
Assigned To |
Both |
|
|
Effort |
Original Estimate |
ADO to OnePlan |
|
|
Due |
Iteration End Date |
ADO to OnePlan |
|
|
Item Type |
Work Item Type |
Both |
Recommended |
|
Name |
Title |
Both |
Required |
|
Iteration (OnePlan) |
Iteration Path |
Both |
Recommended |
|
Parent Id (Structure) |
Parent Item ID |
Both |
Recommended |
|
Points |
Story Points |
ADO to OnePlan |
|
|
Remaining Effort |
Remaining Work |
OnePlan to ADO |
|
|
Start |
Iteration Start Date |
ADO to OnePlan |
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
Important
This table is intentionally left empty. Only choice fields should be mapped in this table to run the SyncLookupToADO strategy.
The following scheduled jobs are installed by default:
OnePlanUpdate
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.
This strategy will bring in all Azure DevOps Epics (or equivalent work item type) and their associated work item types into OnePlan. It is recommended that a filter be put in place to limit what work item types are desired to be brought over. To facilitate large-scale data manipulation, this strategy now efficiently processes multiple records simultaneously. Additionally, for consistency and accuracy alignment between Azure DevOps and OnePlan, the strategy will automatically remove tasks from OnePlan if they are deleted in Azure DevOps This deletion specifically applies to backlog items and does not affect plans within OnePlan.
OnePlanPublish
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.
This strategy will bring in all OnePlan Plans and their associated backlogs into Azure DevOps.
If you want to publish data from OnePlan to Azure DevOps, please make sure that you have a mapping for the "Team Projects Areas" OnePlan field. (see below the mapping details)
If you don't have a field called "Team Projects Areas" in OnePlan, then create a plan level Choice field and name it exactly "Team Projects Areas".
Once you have the plan level field in OnePlan, map it in OneConnect on the plan level in your Azure DevOps integration.
|
OnePlan Field |
Azure DevOps Field |
Direction |
|---|---|---|
|
Team Projects Areas |
Area ID |
Both |
Example:
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 choice field list of options from OnePlan to go into an ADO lookup/choice field options.