Integrating Azure Boards into LinearB

If you use Azure Boards as your project management tool, you must create a Personal Access Token (PAT) to connect it to LinearB.

This guide explains how to generate a PAT, configure the required permissions, and connect Azure Boards to LinearB.

Overview

• Create a Personal Access Token (PAT) in Azure DevOps.
• Grant read permissions for projects, teams, users, and work items.
• Use the PAT to connect Azure Boards to LinearB.
• Once connected, LinearB starts processing board data for tracking and analytics.

---

Steps to Connect Azure Boards in LinearB

Step 1: Create a Personal Access Token in Azure DevOps

1. Go to Azure DevOps and sign in.
2. Click your profile picture (top right) and select Personal access tokens.
3. Click + New Token.
4. Enter a descriptive name (for example, LinearB Integration).
5. Set an expiration date according to your security policy.
6. Enable the following permissions:
   • Projects and Teams: Read
   • Team Dashboard: Read
   • User Profile: Read
   • Work Items: Read
7. Click Create.
8. Copy the token and store it securely. You won’t be able to view it again.

Step 2: Connect Azure Boards to LinearB

Once you have created your PAT, use it to connect Azure Boards to LinearB.

If this is your first Project Management connection

1. Log in to LinearB.
2. Navigate to Company Settings → Project Management → Boards.
3. Select Azure Boards.
4. Paste your Personal Access Token (PAT).
5. Click Connect.

If you already connected a Git provider

1. Go to Company Settings → Project Management → Boards.
2. Click Connect next to Azure Boards.
3. Paste your Personal Access Token (PAT).
4. Click Connect.

After connecting, LinearB begins processing Azure Boards data for project tracking and analytics.

---

Branch and PR Naming Conventions

To ensure accurate tracking, branch and PR names must include the **Azure Boards work item ID**. Work item IDs in Azure Boards are numeric (e.g., `1234`) and should be placed at the beginning of the branch name, followed by a short descriptive title.

Recommended Format

<work-item-ID>-<descriptive-title>

Example Naming Conventions

For PR titles, the work item ID should also be included:

• PR Title Example: Implement user authentication (Work Item 1234)

Matching Git Work to Azure Boards Work Items

LinearB’s Iterations matching algorithm automatically detects the work item ID in the following locations:

1. Branch Names

If a branch is named using the recommended format (e.g., 1234-add-user-authentication), Iterations will recognize that this branch is related to Work Item 1234 in Azure Boards.

2. Pull Request (PR) Titles

If a PR title contains the work item ID, Iterations can still associate the PR with the corresponding Azure work item, even if the branch name doesn’t follow the correct convention.

3. Commit Messages

While branch names and PR titles are the primary sources for work item matching, including the work item ID in commit messages provides an additional layer of tracking.

Example Commit Message:

Refactored authentication flow to support OAuth (Work Item 1234)

By following this structure, developers ensure that all work is accurately reflected in LinearB’s Iterations view, improving visibility and reporting.

Benefits of Using Naming Conventions

Adopting a standard naming convention provides multiple advantages:

• Automatic Issue Linking – Iterations automatically associates branches and PRs with Azure Boards work items, reducing manual tracking.

• Enhanced Iterations View Tracking – Ensures development work is correctly categorized in LinearB’s Iterations view.

• Improved Collaboration – Developers and stakeholders can quickly identify what each branch and PR is related to.

• Streamlined Workflow – Facilitates smoother Git workflows and ensures consistency across repositories.

Best Practices for Naming Branches and PRs

To maximize tracking accuracy and ensure smooth collaboration, follow these best practices:

✔ Always include the Azure Boards work item ID when creating a branch.

✔ Use clear, descriptive titles to indicate the nature of the change.

✔ If a branch was named incorrectly, ensure the PR title contains the correct work item ID.

✔ Standardize naming conventions across teams and repositories.

✔ Educate developers on the importance of consistent naming conventions.

For more information about PATs, see Microsoft’s documentation: Use Personal Access Tokens in Azure DevOps .