In this blog post I’ll show you the fix for the TF51011 exception (refer to the screen shot below),
- Blocked Tasks TF51011: The specified iteration path does not exist. The error is caused by «'Demo\Release 1\Sprint
- Sprint Backlog TF51011: The specified iteration path does not exist. The error is caused by «'Demo\Release 1\Sprint
- Test Cases TF51011: The specified iteration path does not exist. The error is caused by «'Demo\Release 1\Sprint
- Unfinished Work TF51011:The specified iteration path does not exist. The error is caused by «'Demo\Release 1\Sprint
- Work In Progress TF51011: The specified iteration path does not exist. The error is caused by «'Demo\Release 1\Sprint
01 – How to reproduce the exception
- Go to the administration website in the Team web access and navigate to Iterations tab.
- Change the name of your active sprint from what ever its currently named to something else. For example, the current sprint is called ‘Sprint 1’ I’ll rename it to ‘Sprint 1 – Test’.
- Notice the error message, the iteration path does not exists! So, changing the name of the current sprint after you have tagged the tiles breaks the tiles.
02 – Why is the exception raised
Unfortunately, those tiles are tied directly to a work item query and today when you rename a sprint/iteration you have to update the queries manually with the new value. So when you click on the title you will get redirected to the query where you can see the broken query.
03 - Fix
The fix is fairly straightforward, open the queries behind the tiles and change the iteration path to the renamed sprint.
See below, the Work In Progress tile has been fixed!
Note – There are several visual studio extension that let you update the current sprint in work item queries in bulk. For example a good one is ‘TFS Iteration Manager’ that lets you update the current sprint in the work item queries of choice in bulk.
Hope this helps!