- Published on
TF401232 - WorkItem XXX doesn’t exist – Azure DevOps
When you are moving work items between projects/organizations then you should make ID column empty in your CSV file.
Let's say you have following csv file:
ID,Work Item Type,Title 1 ,Title 2,State,Effort,Business Value,Value Area,Tags
"1","Feature","DevOps",,"New",,,"Business",
"2","Feature","User account",,"New",,,"Business",
"3","User Story",,"As a User, I can create my own account","New",,,"Business",
"4","User Story",,"As a User, I can login to application","New",,,"Business",
"5","User Story",,"As a User, I can change my password","New",,,"Business",
"","User Story",,"As a User, I can logout from application","New",,,"Business",
Make the ID column empty, so new IDs can be assigned automatically by DevOps so it looks like this:
ID,Work Item Type,Title 1,Title 2,State,Effort,Business Value,Value Area,Tags
"","Feature","DevOps",,"New",,,"Business",
"","Feature","User account",,"New",,,"Business",
"","User Story",,"As a User, I can create my own account","New",,,"Business",
"","User Story",,"As a User, I can login to application","New",,,"Business",
"","User Story",,"As a User, I can change my password","New",,,"Business",
"","User Story",,"As a User, I can logout from application","New",,,"Business",
💼Open for consulting
I take on consulting and delivery work across .NET and React — on my own or alongside a trusted group of senior engineers I work with. Together we can build, untangle and modernize your software:
- Building ASP.NET / Blazor / C# / WPF apps with Postgres / ClickHouse
- Untangling, refactoring & modernizing legacy ASP.NET, C#, Blazor and WPF into a modern stack (modular monolith C# + React)
- Cloud & on-premise DevOps: Azure DevOps, CI/CD pipelines and automation
- Observability & analytics — in the cloud and on-premise
- On-premise migrations
- Scaling up delivery with experienced .NET, backend and React engineers, plus technical leadership