Andrew Kanieski

Software Architect
Passionate Programmer
Loving Husband & Father of Three

Github LinkedIn Email RSS Feed
.net .net core artifactory azure azure devops azure devops server azure devops services azure-pipelines azure-pipelines-agent build chatops cleanup cognitive service computer vision concurrent-jobs containers cv cve-2021-42574 devops devsecops dns dotnet dotnetcore frontdoor gist gists git githooks github gitleaks hugo index invisible isolated shell jfrog kubernetes linux memory memory-dumps microsoft teams netcore package management packages parallel-jobs pat pats pipelines pre-commit proxy secret-scanning secrets security service now servicenow smc sonarqube ssh static site generators teams tfs tfvc tokens trojan trojan-source-attacks visual studio vsts webhook
Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer’s view in any way.

Mapping Azure Repo Links After Work Item Migration

Posted on November 16, 2021 | 1 minute read

There are a number of open source tools for migrating work items from one Azure DevOps Organization to another and even from Azure DevOps Server to Azure DevOps Services. But what happens when you migrate a work item from the source that happens to reference a Branch, Pull Request or Commit that exists on an Azure Repo that used to reside in the source, but now lives inside the target?

If the open source tool your using does not support mapping between the Git Repo Links you may find yourself with work items that have broken Git Links.

They will look something like this when they fail to map to a proper linked Git Repo:

UI Screenshot

Fortunately, the Azure DevOps SDK is fairly robust and easy to work with. Couple this with a quick development environmenet courtesy of GitHub CodeSpaces and we have an easy solution to this problem: a simple command line tool that maps git links on the target work items that reference repos in the source by repository name.

See the code below, or download the latest executable from the GitHub Releases Page

Lookout for upcoming articles on GitHub CodeSpaces and some tools around tracking down Trojan Source Attacks!

Happy Coding!

– Andrew Kanieski

Share via

Tags:azure devops azure devops services devops vsts


Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer’s view in any way.


comments powered by Disqus