Limitations of Unito's AzureDevOps Integration

Here's a breakdown of what Unito's Azure DevOps integration can't do yet — and a few other considerations.

Unito's Azure DevOps integration is designed to get crucial data out of your projects and into other tools. You've seen what Unito can do for Azure DevOps users, so this article will cover what it can't do — yet.

What this article covers:

Unsupported fields

While Unito's integration for Azure DevOps supports most of the tool's fields, here are some it doesn't support.

  • Multiline Text Custom Fields
  • Attachments

Other limitations

  • 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.
  • Blocks of work: You can't use boards as your block of work when syncing Azure DevOps. You have to pick a project
  • Live sync: Because the Azure DevOps API doesn't support webhooks, data will only be synced to and from this tool every five minutes.
  • Epic hierarchy: For now, Unito can't sync epics as parent tasks and replicate the hierarchy within them in other tools.

Other Azure DevOps considerations

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.

If you have multiple DevOps organizations, make sure this setting is turned on across all of them.