Our Azure DevOps integration is live! Because it's still in beta, here are a few things you should know.
How does this beta work?
When an integration on the upcoming integrations page gets enough interest, we start working on adding it to the Unito toolbox. We then release a beta version of the integration so you can get access to it earlier. That opens it up to your feedback so we can tailor it to better fit your use case.
Our Azure DevOps (ADO) integration is now in beta, meaning you can start connecting to your Unito account right now! However, there are a few differences between a beta integration and a regular integration that you should know about.
A demo of this integration in action
Follow our step by step guide to connect Azure DevOps to Wrike or watch this demo with Zendesk below:
Supported fields and other features
Beta integrations don't always support as many fields as their full-featured counterparts. Here are the fields you can sync with our Azure DevOps integration, along with which fields can be used in rules.
If there's something you'd like to see from this integration that we're not doing yet, please reach out to us! Your feedback helps us focus our efforts.
What counts as an item in sync?
For Azure Devops, Unito counts every synced issue as an item in sync.
Custom fields
The custom fields supported by our ADO integration are User, Number, Dropdowns, Text (Single line), Boolean, Date Time, and Swimlane.
Limitations and other things to keep in mind
Because this integration is still in beta, there are some things you won't be able to do.
-
Default work item type: When a new work item is created in Azure DevOps by Unito, it will always be one type of work item, whether that's an Issue, an Epic, a Feature, or a Bug. You can set the default item type using a rule or change the item type manually in Azure DevOps after it's created.
-
Signing up via Azure DevOps: You'll have to use a different tool account — or an email address — to sign up for Unito.
-
Syncing attachments: You won't be able to sync your Azure DevOps attachments to other tools just yet.
We can't wait to see what you do with this ADO integration. If you have any questions or feature requests, please reach out to us with the chat bubble! We'll be happy to help.
Third-party application access
In order for Unito to access your Azure DevOps projects, make sure that your DevOps Organization Policies allow for Third-Party Application access via OAuth. To enable it, go to your Organization page. Then select Organization Settings, scroll down to Policies, and toggle Third-Party Application access via OAuth under Application connection policies.
.png)
If you have multiple DevOps organizations, make sure this setting is turned on across all of them.
Did this answer your question?