Integration with ADO Boards

In this Help article, we will guide you to integrate successfully with ADO Boards

Step 1 - Find the ADO Integration page for system intergation

In the integrations panel, select ADO Boards, once you reach inside follow the next set of instructions.

Step 2 - Add your base URL

1. Use your ADO base URL e.g. https://dev.azure.com/myorg 

Step 3 - Create your API  token   

1. Login to your Azure Dev Ops account.

2. Click on settings and initiate the creation of you personal access token.

3. Ensure that you select the correct organization.

4. Click on "+ New Token" to trigger creation of a new token.

5. In the new creation workflow:

5.1 Provide a valid name.

5.2 Select the relevant organization and provide a custom defined expiry period (we recommend the expiry period to match the license duration e.g. if the license duration is a year then set the PAT expiry to 1 year).

5.3 Select "custom defined" for scopes.

5.4 Select the following scopes for Cubyts <-> ADO integration: GitHub Connections - Read, Project and Team - Read, Work Items - Read

6. Copy the token to configure the same in Cubyts.

Step 4  - Use the configured token, email id and the ADO org URL to trigger integration with Cubyts

Step 5  - Configure Sources

1. Select a relevant project.

2. For the chosen project, select the relevant areas for the teams in the project.

3. Select the portfolio work item type level and all the relevant work item types for the chosen level.

4. Select the work item type level and the associated work item types that must be analyzed by Cubyts to discover flags.

Step 6  - Configure roles (optional)

1. The platform will list all the users (with a certain authorization) from the configured URL; select the role for those users to aid classification of work items.

Step 7 - Advanced settings (optional)

1. Select the effort estimation methodology used by the team in the chosen project (you can choose between storypoints and ideal days depending on whether relative or absolute effort estimation method is used by the team).

2. Select the effort estimation fields configured in ADO for the chosen work item types (in the sources tab), this configuration shall be used by Cubyts to perform Planned Vs. Actual effort analysis.

3. Select the attribute in the chosen work items that represents the name of the product manager who owns a work item (from an execution standpoint), this will be used by Cubyts to filter work items in trace reports.

4.  Map ADO priorities with Cubyts priorities (for every priority scheme)

The platform automatically extracts all the (unique) ADO priority schemes and automatically recommends a mapping to corresponding Cubyts priorities. The user can override the platform recommendations, and remap if needed. This configuration is used by the platform the automatically prioritize flags which can help the users plan their resolution.

Step 8  - Map issue workflow with authorized roles (Optional)

Use this configuration for the following: 

1. Identify the right roles for state transition or workflow transition.

2. Identify whether a transition is mandatory.

This configuration can be used to identify if there are commits in a PR or a feature branch that are mapped to issues which have missed the configured workflow.