Sync Work Items Between Multiple Team Projects on Azure DevOps: the Good, the Bad, the Ugly
summary
A working pipeline migrates and continuously syncs Azure DevOps work items using Service Hooks and Azure Functions and REST calls, creating destination items, copying fields and links, and surfacing attachments with partial fidelity. It runs in production and handles many cases but hits limits: area path and test‑suite mapping require manual templates, personal access tokens and webhook retries cause fragile auth and monitoring, and near real‑time at scale (millions/month) needs careful throttling. One‑way sync by default; two‑way possible but complex.
AI-written summary · about
chapters (9)
- 0:00Azure DevOps work items intro
- 2:55Two-way sync of work items
- 8:40Real-time vs non-real-time
- 15:01Test suites and test plans
- 21:46Area and iteration paths
- 25:00Edge cases and pitfalls
- 31:36Pros and cons
- 35:35Manual updates maintenance
- 36:59Alternatives and tools
related talks
27mBuilding powerful DevOps pipelines with Microsoft Azure DevOps
50mCode repos and automated deployment
46mAutomating Infrastructure as Code with Azure DevOps
41mBattle tested project planning with Azure Devops boards
01h 02mTales from the Azure Migration Trenches
03h 08mWorkshop
42mAzure DevOps security - Lessons learned
01h 01mAgile Evolution: An Enterprise transformation that shows that you can too