Export Azure DevOps Pull Requests to Excel

Why the pull request list is not enough

The pull request list in Azure Repos is built for working through open reviews. It has no export button, and it shows one page of results at a time. For a retrospective, an audit or a team report you need the history as rows.

What the workbook should contain

1. One row per pull request with its repository, source and target branches, author and status.
2. Reviewers and their votes, plus the number of iterations and comment threads.
3. Created and completed dates as real Excel dates, so they sort and filter correctly.
4. The count of linked work items.

Pick a date window first

Decide the period before you export. A quarter is usually enough for a review-process discussion. A very wide window on a large organization means thousands of pull requests, and each one needs extra calls for reviewers, threads and work items, so it takes longer.

Do it from the browser

The extension adds a hub under Repos. It reads the data with your own Azure DevOps session, builds the .xlsx in the browser and downloads it. There is no pipeline to configure, no personal access token to create and no Cody Labs server in the path.