The following diagram illustrates the general scheme of field mapping when an Azure DevOps Project is mapped to a Jira Align team.
The following diagram illustrates the general scheme of field mapping when an Azure DevOps Project is mapped to a Jira Align portfolio.
All users added to Jira Align through the connector automatically receive the Developer team role and the system role selected in the Default Jira Align system role for ADO users dropdown.
Users added to Jira Align sprints through the connector automatically receive the Developer role.
Allocations
If a user is a member of only scrum (Agile) teams, they will receive an allocation of 100% for each sprint. If a user is a member of two or more sprints within one anchor date, their allocation of 100% will be equally distributed across these sprints.
When a user is added to a Kanban team, allocations are re-calculated to be equally distributed across all Kanban teams and team sprints within the present anchor date range, for a total of 100%.
As a simple example, a user is a member of two Kanban teams, Team A and Team B. Both teams have an anchor date range for the current month.
She’s also part of an Agile team, Team C. This team has two sprints during the current month.
When the user is added through the connector, her allocations for each Kanban team and Agile team sprint will be calculated as:
100% / (2 sprints user is added to within the current anchor date + 2 Kanban teams) = 25%
Print 
PDF
Join the Atlassian Community!
The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.
Need to contact Jira Align Support? Please open a support request.