Managing Project Trackers in Azure DevOps

• Create delivery trackers scoped to Azure DevOps projects, teams, and areas.
• Combine multiple filters to accurately reflect real work ownership.
• Use AND / OR logic to control how work items are collected.
• Edit or delete trackers as delivery scope changes.

Project trackers in LinearB define what work belongs to a given team. When using Azure DevOps, trackers allow you to scope delivery metrics by project, team, area paths, and backlog attributes.

This ensures delivery insights and metrics accurately reflect your team’s actual workload and ownership.

Ensure your Azure DevOps integration is connected before creating a project tracker.

If not connected, follow: Connect LinearB to Azure DevOps

1. Navigate to Projects → Delivery.
2. Click Create Project.
3. Enter a unique Project Name (cannot match an existing team).
4. Under Project Scope, click + Add Filter and select:
   • Project
   • Team
   • Area path(s)
5. Choose a methodology (Scrum or Kanban).
6. (Optional) Add additional filters such as:
   • Epic
   • Feature
   • Tag
   • Custom fields
7. Click Save to activate the tracker.

LinearB combines project filters using Boolean logic:

• Same filter type (projects, teams, areas): combined with OR
  (Project A OR Project B)
• Different filter types: combined with AND
  (Project A OR Project B) AND Area X

This ensures only work items that meet all required conditions are included in the tracker.

1. Click the ⋮ menu next to the tracker.
2. Select Edit Project.
3. Update scope, filters, or methodology as needed.
4. Save changes (updates apply within ~15 minutes).

Click the ⋮ menu next to the tracker and select Delete Project.

• Azure DevOps supports complex area path hierarchies—select all relevant paths.
• Large scope changes may impact historical delivery metrics.
• Teams can create multiple trackers to separate different work streams.