Azure DevOps integration

Integrations are configured in two layers: an account connection (under Integrations) and a per-project mapping on the project's Azure DevOps page.

Recommended setup flow

• Prepare Azure credentials with work item read/write access to the target project. The fastest path is a Personal Access Token (PAT) with Work Items (Read & Write), Project and Team (Read), and Identity (Read) scopes — no OAuth app registration required.
• Create or verify your account-level connection at Account → Integrations (PAT or Entra service principal).
• From the project, open the Integrations page (project header menu) and click Configure on the Azure DevOps card to select the connection and defaults.
• From an action, use the Azure DevOps control to create or link work items. An action can link up to 20 work items; use Add work item to link another, or enter several ids separated by commas.

Connection scope

When creating a connection, scope controls which Action Log projects may use it: either all projects or a specific list. The project mapping page only lists connections you are allowed to use for that project.

Mapping fields

• Default work item type: The Azure DevOps work item type used when Action Log creates an item (for example Task or User Story).
• Area Path / Iteration Path: Optional DevOps fields applied to new work items so they land in the right backlog area and sprint.
• Default tags: Tags appended to created work items for traceability.

Sync behavior

Action Log creates or links work items when you use the in-app DevOps actions (for example pushing an action to Azure DevOps). It does not automatically import your entire Azure DevOps backlog into Action Log.

• Linked actions are checked hourly in the background. When meaningful fields change (title, state, or assignee) or the DevOps link becomes unavailable, an update is added to the action so your team can see what changed. A DevOps icon appears next to the action in table and kanban views when a link is active. When several work items are linked, the icon shows a count; click it to see each one.
• You can trigger a manual refresh for one work item, or Refresh all, from the action's Azure DevOps panel at any time. If changes are detected, your team receives a notification.
• Action Log does not change your Action Log action status from Azure DevOps state.
• Sync runs in the background; opening a project or action does not trigger a full DevOps sync.
• Active DevOps connections are health-checked daily. Project owners/editors are notified only when a check fails (email + in-app), not when checks succeed.

A healthy connection means credentials and permissions remain valid; if a connection is unhealthy, re-check the PAT or secret and project access in Azure DevOps.

Removing an account connection

Removing an Azure DevOps connection clears every project mapping and every DevOps work item link that used it. The Integrations page asks you to confirm first. OAuth connections offer Reconnect when you only need to re-authorize. PAT connections are updated by pasting a new token in Edit when the PAT expires.

Troubleshooting checklist

• Confirm the selected connection is in scope for the current project.
• Confirm credentials can read and write work items in the configured Azure DevOps project.
• Verify configured work item type, area path, and iteration path are valid in Azure DevOps.
• If linked-item details look stale, wait for the next hourly sync or use the manual refresh button on the action's Azure DevOps panel.
• If your owners/editors receive a daily connection-problem alert, use Integrations to retest and repair the connection before the next daily check.

By default, this integration is action-driven from Action Log into Azure DevOps. If your team needs bi-directional update expectations, align on process before rollout.