Need to know what fields and rules are supported by this integration? Here's your full guide.
What does this article cover?
Fields you can map with Unito's Azure DevOps integration
Unito's integration for Azure DevOps supports over a dozen fields. Here's a list of them, and a few examples of what they can be mapped with in other tools.
| Azure DevOps Field | Example mapping |
| Title | Titles in other work items, like Jira issue titles or Trello card names. |
| Description | Descriptions in other work items, from Jira issues to Asana tasks. |
| Due date | Typically synced to due dates in other tools. |
| Status | Columns in Trello, State in Jira, Status in Asana |
| Comments | Messages in Slack, Comments in Jira |
| Assignee | Assigned to in ServiceNow, Assignee in Jira |
| Tags | Labels in Jira |
| Work item type | Issue type in Jira |
| User* | Custom text field in Asana |
| Number* | Google Sheets column, Custom number field in Asana |
| Dropdown (String Picklist)* | Dropdown in monday.com |
| Dropdown (Number Picklist)* | Single-select field in Asana |
| String* | Custom text field in Asana, Description in Jira |
| Boolean* | Checkbox in Airtable |
| Date time* | Date field in Jira |
| Swimlane | Description field in Jira |
| Effort | Description field in Jira |
| Story points | Story point estimate in Jira |
| Remaining work | Description field in Jira |
| Acceptance criteria | Description field in Azure DevOps |
| Iteration | Fix version in Jira |
| Priority | Priority fields in other tools |
| Test cases steps | Description field in ServiceNow |
| Area path | Description field in other tools |
| Closed date | Matched with Closed date fields in other tools |
| Created by | Reporter in Jira |
| Attachments | Attachments are usually synced to the description of other work items, allowing users to open them there. |
| Start date | Sprint start date in Jira, Start date in Asana. |
| Column | Column in Google Sheets |
*Custom field
Rules supported by Unito's integration
Unito's rules allow you to filter out ADO work items (e.g. epics, issues, and tasks) you don't want synced to other tools. Here are the fields you can use in Unito's rules and a few ways you can use them with other tools you can integrate with Unito.
- Status: If you don't want to sync your entire backlog to other tools, you can filter out any backlogged issues with this rule. You could also set up rules that automatically sync work items when they hit a certain status to get input from other teams.
- Assignee: If certain developers are working on projects that cross department barriers, you can use this rule to only sync issues they're involved in to other tools. Similarly, if you have assignees in ADO working as intermediaries between two tools, assigning an issue to them can get it synced across.
- Tags: With tags giving you the ability to organize ADO work items any way you like, being able to filter them with Unito rules allows you to support just about any workflow.
- Work item type: ADO has multiple work item types, and you can choose which ones you want to filter out of your Unito integration.
- Dropdowns: These fields are incredibly flexible, and Unito's rules are as well. Filter out work items based on specific options in your dropdown to support ticket escalations, agile development, and other workflows.
- Area path: ADO's area paths allow you to organize multiple developers into specific functions, and Unito rules help support that organizational structure as you sync ADO work items to other tools.