I was pleasantly surprised this week when I dived into TFS Online to tweak some queries and stumbled upon the new @CurrentIteration token that can be used.
This token can potentially solve the administration overhead associated with getting consistent reports out of TFS from sprint to sprint.
In the past I have had a series of TFS Queries to track the progress of things happening within the sprint such as:
- Outstanding Product Backlog Items (with associated outstanding child work items shown in tree view)
- Outstanding Product Backlog Items (flat list)
- Done Product Backlog Items
The problem with these queries was that each of the queries has to conditional match a specific sprint (iteration)
The new @CurrentIteration token can be used to dynamically work out what the current iteration (sprint) is so that you don’t have to manually update all the queries when the sprint changes.
Here’s a post from Microsoft…
View original post 82 more words