This article describes the Azure DevOps Team Projects 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
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
- 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.
Plans - Team Projects
OnePlan Fields |
Azure DevOps Fields |
Direction |
Notes |
---|---|---|---|
Name |
Project Name |
Both |
Required |
Owner |
Owner |
Both |
Required |
Backlog - Items
OnePlan Fields |
Azure DevOps Fields |
Direction |
Notes |
---|---|---|---|
Assigned To |
Assigned To |
Both |
Required |
Due |
Finish Date |
ADO to OnePlan |
|
Item Type |
Work Item Type |
Both |
Required |
Name |
Title |
Both |
Required |
Parent Id (Structure) |
Parent ID |
Both |
Recommended |
Points |
Story Points |
ADO to OnePlan |
|
Start |
Start Date |
ADO to OnePlan |
Lookup Tables – Pick List Lookup
OnePlan Fields |
Azure DevOps Fields |
Direction |
Notes |
---|---|---|---|
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 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.
These strategies are available to be scheduled but are not installed by default. Please 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.
Comments
0 comments
Article is closed for comments.