Key Result from Azure DevOps


The ADO data connector for WorkBoard allows the user to pull progress based on available queries in ADO and specified issue status.

Once you've created an objective, you can create a key result that pulls data from your Azure DevOps projects; as work items are completed in Azure DevOps, your key result is automatically updated to reflect the progress made.


  • The IT admin for your organization may need to approve the connector for the first time if the App is configured to require approval.

Add Key Results from Azure DevOps

  1. Hover over your Objective and click the Kebab.mceclip0.png
  2. Select Edit Settings.
  3. Select Add another Key Result.
  4. Select Advanced Options.
  5. Choose Pull data from external applications.Screen_Shot_2021-10-20_at_3.11.09_PM.png
  6. Pick Azure DevOps from the list of integrations.mceclip0.png

Note: To create your first key result sourced from Azure DevOps, you'll be asked to authenticate to an Azure DevOps instance through OAuth or by providing a PAT (personal access token). 

Once you are authenticated, select a project within your Azure DevOps instances by searching for its name. 


Measure by Work Item ID, Work Item Name, or Saved Query

After selecting a project, you'll have the option of entering work item IDs, searching for specific work items by name, or selecting a saved Azure DevOps query.

Work Item ID and Work Item Name

WorkBoard has three ways to measure your progress from Azure DevOps:

  • Only the specified Work Items: Measures the specific Work Items you include. This is good for measuring progress on a specific subset of Work Items and will not include any hierarchical children.
  • Progress by All Work Items (Rollup): Measure progress similar to the “Measure Progress by all Work Items” “Rollup” column available in an Azure DevOps Backlog Board. This will NOT include the specified Work Item themselves but will include progress on all Work Items hierarchically below the specified Work Item(s). See here for Azure DevOps documentation on Rollups. This works well for any hierarchical relationships between Work Items and progress.
  • Selected Work Items and any children: Measure only the Work Items that you have identified, or both those Work Items and their immediate children (this is the child link relationship in Azure DevOps).

Tip: When you are searching for work item names, make sure to search for entire words within your work item names to bring up search results.


Saved Query

  • WorkBoard will gather the count of Work Items in the query. The count will be total number of work items slated for completion during the OKR time period.
  • You can select the set of statues associated with work items that are considered completed work in your project and workflow. Completion percentage for these key results will be based on the total number of work items in the query, and how many of them are considered "Done" based on your selections. 

Tip: You will want to select queries that pull items from a single project; especially if you have different custom statuses defined per project.

Status selection when configuring a key result is based on the custom statuses defined for the one project you select in the key result creation workflow.  

Synchronizing Data from Azure DevOps

WorkBoard will pull data for the KR directly from Smartsheet following the cadence specified.  The Business Result Owner also has the ability to “sync data now” to pull data in real-time.

There are two ways to sync data for your Key Results.

Force a Sync on a Single Azure DevOps Key Result:

  1. Select Key Result to go to the Key Results Details page.
  2. Choose the Kebab menu in the upper right-hand corner.
  3. Select Sync Integration Data.

Force a Sync for all Key Result Integrations:

  1. From the My Objectives Page, select the Kebab icon in the upper right-hand corner.
  2. Select Sync Integration Data.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request