OnePlan and PowerApps - How to Set Up

This article explains how to set up the integration between your OnePlan group/environment and PowerApps / Dynamics environment.

Before beginning, the following assumptions are made in order for this integration setup to be successful:

• Office 365 is up and running

• A PowerApps or Dynamics environment us up and running

• OnePlan group is setup in the same Office365 tenant

OnePlan Setup

In order to do the OnePlan setup, you need to be an admin, meaning you are a user with Owner permissions in OnePlan. If the Advanced Settings are enabled for your group, continue to the next steps. If the Advanced Settings are NOT enabled, skip to the alternate steps below.

1. Log in to your OnePlan group with your Office365 account.

2. Open the Admin pages by clicking on the Settings gear.

3. Select Integration in the admin navigation.

4. Click the + (plus) icon in the Authentication Keys section.

5. Save the key name & generated key somewhere (such as in a notepad doc), as once you navigate away, the key cannot be seen. To be used at a later step in the OneConnect configuration.

PowerApps / Dynamics

PowerApps / Dynamics permissions?

Log in to your organization's PowerApps environment ex: https://hybridppm.crm.dynamics.com/

On the top right-hand corner, click on the Settings Gear, then Advanced Settings. Then click Settings, then Security, then Users, and verify that the user you will be setting up the integration with is a System Administrator and a System CustomiZer.

Login to the Azure Portal with an account that has permissions to create an App Registration. https://portal.azure.com/

1. Navigate to Azure Active Directory.

2. Click on App registrations, then New Registration, name it whatever you would like, and select Accounts in this organizational directory only, leave redirect URL blank.

3. Click on Authentication and Set Implicit grant to ID Tokens

OneConnect Setup

You must be logged in as the Tenant Admin.

1. Go to https://my.oneconnect.ai

2. Configure the following integration: OnePlan and Azure DevOps Epics. Click the Configure button.

ONEPLAN

1. Authentication Key: Enter/paste the OnePlan Key that you saved from the earlier OnePlan Setup steps.

2. Click the Next button.

INTEGRATOR

Click the Next button.

AZURE DEV OPS

1. Your Azure DevOps URL: Enter your organization Azure DevOps URL that you also used to create the token.

2. Your Azure DevOps API key: Enter/paste the Azure DevOps token key from the earlier Azure DevOps token steps.

Expand Additional Options:

Allow user to select which Work Item Types under Epics to bring into OnePlan as backlog work type under tasks. By default, the value will be Task and Bug if none specified.

Click the Next button.

Integration Information

Functionality

This integration has two 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).

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
Name	Title	Both
Team Projects Areas	Area ID	OnePlan to Azure DevOps
Owner	Assigned To	Both

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

OnePlan Fields	Azure DevOps Fields	Direction
Name	Title	Both
Parent ID (Structure)	VSTS Parent Item ID	Azure DevOps to OnePlan
StartDate	Start Date	Azure DevOps to OnePlan
EndDate	Finish Date	Azure DevOps to OnePlan
AssignedTo	Assigned To	Azure DevOps to OnePlan

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

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

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.