Azure DevOps

In Teamhood, we took two-way integration with Azure DevOps to a whole new level. Your business team together with product people, can finally create and manage work items hassle-free. Now, you can leverage Teamhood’s advanced, yet easy-to-use, user interface on top of Azure DevOps work item store as a database. But that’s not the end of it!

Items are added and synced in a near real-time manner. Whether you’re adding, updating, or deleting items, the coordination between Teamhood and Azure DevOps ensures seamless and instant updates. Collaboration has never been easier by joining these two systems. 

On top of everything, Teamhood offers a unique scriptable/config-driven integration view. This view allows power users to create powerful variations for each unique use case.

How to connect Azure DevOps to Teamhood?

To kick things off, here are the main prerequisites:

  1. Admin access to Azure DevOps project(s)
  2. Personal access token (PAT). How to get one
  3. Azure DevOps organization URL, i.e. https://dev.azure.com/{yourorganization}

Create a new integration and configure it

  1. Open existing or create a new Teamhood workspace which you will use to integrate with Azure DevOps.
  2. Navigate to Workspace Settings -> Integrations
  3. Select the board location where integration will place work items
  4. Enter your organization URL and personal access token (PAT)
  5. Click connect
  6. If connected successfully, you will be presented with the integration config
  7. Either use the default one or start modifying the config and fine-tune what you want to integrate
image 11

We strongly recommend reading the integration config documentation to understand its full power better.

For those who would like to see everything in action, check the below video guide.

How does it work?

Work item synchronization

Azure DevOps -> Teamhood

  • Teamhood queries Azure DevOps based on defined item types from defined iterations in the integration config.
  • Teamhood takes mapped properties for each item type.
  • The integration engine runs the synchronization to:
    • Create new items that are not present in Teamhood yet
    • Update existing items which are already present in Teamhood
    • Remove out scoped items based on integration config
  • Integration sync runs every hour or every custom-defined period.

You can also trigger a manual synchronization whenever in a need. Just click on the integrations box near the Board title and hit “Sync now”.

image 1

Teamhood -> Azure DevOps

  • Once you perform any action on an Item in Teamhood, it will check if it is subject to update Azure DevOps.
  • If this action is subject to the update, it will be immediately sent and validated to Azure DevOps.
  • If there is no issue, it will be committed, and nothing else needs to be done.
  • In case of failure, the user will be presented with a red error message

How often data is synchronized?
Teamhood runs synchronization hourly to check for new or updated work items. Or you can run it manually when needed.

Integration config

image 12

This is the main power of integration engine. You can customize and map out unique variations for every use case. Make it simple or full of power with our intuitive developer-grade config editor. Integration config documentation.

Troubleshooting

⚠️ If your DevOps integration stops working or you see a warning message – navigate to the Workspace Settings -> Integrations page and check the error.

Teamhood uses cookies, to personalize content, ads and analyze traffic. By continuing to browse or pressing "Accept" you agree to our Cookie Policy.