This article describes OnePlan's recommendations and best practices for the Azure DevOps Epics integration.
In OnePlan, the default Plan Types are: Portfolio, Program, Project, Epic, Objective, Idea, and Key Result. If the Work Item Type is of any other value than the above list, then the plan will be imported, but it will not be imported correctly and might be considered “missing”.
While in OnePlan, navigate to Config > General > Plan Types > Add Type. Add the Work Item Type to the desired hierarchy level. Once complete, feel free to run the OnePlanUpdate strategy against a single plan to verify it worked.
This field is case sensitive, if the values do not match exactly, the plan type field will remain blank.
To check if your plan was brought in, go to Home > Plans > All Plans. Type in the name of the plan, if the plan is there, look at the Plan Type column. If it is blank, then you need to manually change this to a valid plan type via the Reorganize button on the left side of the plan name.
Check the box Allow creation and editing of work items in OnePlan to be brought into Azure DevOps.
The field mappings desired to go in both directions are set correctly (Please do not modify any of the fields marked as Required in the Field Mappings section). To alter this, click on the arrows between the options saved.
Add Value Mapping to any values that do not match between Azure DevOps and OnePlan. This is mainly used with Multi-/Choice fields.
We are excited to announce that we now support multiple Azure DevOps Epics integrations to the same OnePlan group!
Each integration will be connected to a single Azure DevOps Organization.
We highly recommend that each integration is given its own OnePlan Authentication Key.
For synching purposes, we recommend that each integration be given a unique name, this name will be used to differentiate between the Azure DevOps Organizations when exporting data from OnePlan.