Integration with ADO Boards

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

Step 1 - Find the Jira Integration page for system intergation

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

Step 2 - Add your base URL

1. Use your Jira base URL e.g. https://company.atlassian.net

Step 3 - Create your API  token   

1. Use this link to create the API token -  https://id.atlassian.com/manage-profile/security/api-tokens

2. Once the link is opened;

    a. Click on the 'Create API token' button

b. Give your token a name 

 c. Copy this token and add it to the respective field provided in Cubyts

Step 4  - Add your email ID

1. Use the email ID used to create your account in Jira

Step 5  - Configure basic conditions (mandatory)

1. Select relevant projects and epics for this workspace.

2. Select the list of issue types that must be analyzed by the platform.

3. Help the platform understand the definition of features in your set-up.

Step 5  - Configure roles (optional)

1. The platform will list all the users (with a certain authorization e.g. creators of issues, assignees of issues, users with comment rights, users with issue transition rights) from the configured URL; select the role for those users to aid classification of issues.

Step 6  - Configure dependencies (optional)

Use these settings to configure a variety of dependencies e.g.:

1. Configure attributes in Jira that depicts dependencies (they can be standard or custom attributes), these attributes are typically used to drop linked issues from another project (this is relevant for companies that do not use Jira issue links).

2. Identify dependent projects (in other words, what are the projects that are related to the configured projects in the sources tab).

Step 7.1  - Map Jira priorities with Cubyts priorities (for every priority scheme)

The platform automatically extracts all the (unique) Jira 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 7.2  - Identify types of projects (optional)

This configuration is applicable only for those teams which have highly customised Jira and typically end up executing different types of jobs in different projects (e.g. one project for UX/UI design and a completely different project for product management/engineering).

1. Identify the projects used for a certain type of job (from the projects specified in the source tab and the dependency tab).

2. Identify dedicated issue types in those project that represent a type of job (E.g. a custom issue type for definition work).

3. Identify attributes that are typically used to drop deliverables.

4. Companies that use standard issue types may use labels to represent a type of job (E.g. An issue type story labelled as Design may represent a UI design story).

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

Use this configuration for the following (this has to be done for every project selected in the sources tab):

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. 

Note: You may also integrate with Jira for support, the steps to integrate and steps to configure the boundary conditions are the same (however only the relevant projects and issue types - see step 5, has to selected by the user).