Why Are No Issues Fetched After Setting Up the PM Integration in Azure DevOps?

When configuring Project Management (PM) Integration in CodeScene for Azure DevOps, you might encounter a situation where no issues are fetched, even though all settings appear to be correct.

This behavior can occur when your repositories and work items are hosted on the same on-premises Azure DevOps Server but belong to different projects.

Understanding the Cause

CodeScene needs to know not only which server or collection (organization) to connect to, but also which specific project within that collection contains the work items. Normally, both the organization (collection) and projects are automatically extracted from the repository URLs. However, in configurations where repositories and work items reside in different projects, this automatic extraction isn’t sufficient. If this information isn’t explicitly provided, CodeScene may connect successfully but fail to retrieve any issues.

How to Fix It

When setting up the PM Integration, there’s an option to specify the Azure Organization field.

  • This field is equivalent to specifying the collection name.

  • Once the collection (organization) is entered, CodeScene will display an additional setting on the second page of the PM Integration configuration that allows you to select the specific project from that collection.

By selecting the correct project, CodeScene can then access and fetch the relevant work items successfully.

Summary

If no issues are fetched after configuring the PM integration for Azure DevOps:

  1. Verify whether repositories and work items belong to different projects.

  2. Ensure the Azure Organization (collection) field is filled in.

  3. On the next configuration page, select the correct project where the work items reside.

Following these steps should resolve the issue and allow CodeScene to retrieve your Azure DevOps work items as expected.