Skip to main content
Version: Version 22

Azure DevOps teams

Introduction​

What is Azure DevOps team configuration? After setting up the Azure DevOps application link, you configure how Azure DevOps teams are used in Fortes Change Cloud. This involves creating a team configuration (which defines the connection settings, field mappings, and synchronization behavior) and then adding teams that become available in FCC portfolios, programs, or projects.

The level at which teams are configured determines whether data exchange happens at portfolio level (Epics) or program/project level (Features).

Who uses it?

  • Administrators and integration specialists who configure the Azure DevOps integration.
  • Portfolio and program managers who use Azure DevOps teams in FCC to align planning with development execution.

What value does it deliver?

  • Links Azure DevOps teams to the correct level in FCC, enabling structured and automated data exchange.
  • Keeps FCC planning and Azure DevOps work items in sync through field mappings and webhook-driven updates.
  • Supports both live synchronization (top-section field mapping) and initial linking (bottom-section field mapping) for flexible integration.

Create a new configuration for team setup​

:::note Prerequisite This requires an Azure DevOps application link. Configure teams at portfolio level to link with Epics, or at program/project level to link with Features. :::

After setting up the application link, the next step is to create a team configuration. Open the Manage configurations panel and click + Add configuration.

All fields in the configuration are required, except for the assignment field.

The configuration uses the selected Application Link to connect with Azure DevOps. This connection allows Fortes to retrieve the correct values for the dropdown menus:

  • Organization: the top-level unit in Azure DevOps.
  • Process: defines which item types are available within a project and which fields must be present.

Field mapping​

Field mapping determines how Fortes (FCC) items and Azure DevOps work items are linked.

  • Top section (live updates)
    This section is used by the webhook. Whenever a field changes in Azure DevOps, the corresponding FCC field is updated automatically in the linked FCC item.

  • Bottom section (initial mapping only)
    This section is applied only once, when an FCC item is first linked to a work item.

    • If FCC fields are updated later, the changes will not be pushed to the Azure DevOps work item.
    • Likewise, updates from Azure will not flow back to these fields.

In short: the top mapping keeps fields in sync, while the bottom mapping is only applied at the time of the initial link.

Add a team​

To connect Azure DevOps teams with Fortes Change Cloud, you first need a valid team configuration (created in the previous step). Once that is in place, you can add teams as follows:

  1. Click + Add Team above the team configuration list.
  2. In the form, enter the Name of the team.
    • Optionally, add a Short Name (3 letters) for quick identification.
  3. If you want team members to be able to register time in Fortes Change Cloud, add them in the Members for Time Registration field.
  4. Select the correct Configuration (created earlier) in the dropdown.
  5. Choose the Project, Area Path, and optionally the Iteration Path.

Finally, click Create to add the team. The team now appears in the team overview list.

Best practices​

  • Reuse one configuration for teams that share the same Organization and Process, instead of creating a configuration per team.
  • Map only the fields that must stay aligned in the top (live) section; use the bottom section only for values you set once at link time.
  • Add only the necessary members to Members for Time Registration to keep time entry focused.

FAQ​

What is the difference between the top and bottom field mapping?
The top section keeps fields in sync live via the webhook; the bottom section is applied only once, when an item is first linked.

Do I need a separate configuration per team?
No. A configuration can be reused across teams that share the same Organization and Process.

At what level should I configure teams?
Configure at portfolio level to link with Epics, or at program/project level to link with Features.

Need more support?​

For step-by-step instructions or troubleshooting, contact your Fortes Change Cloud administrator or consult in-app help.