Feel free to reach out if you can’t live without this one.
One of our awesome clients came up with a clever solution to the problem of queries for the “current” iteration in TFS.When we saw it, we couldn’t wait to share it with all of you, and who better to explain it than the person who devised it? Since upgrading from TFS 2010 to 2013, one of my favorite additions has been the date attributes on iterations.And with Past, Future, and Current reflected in the iteration path itself, those designations become queryable. This way, as each iteration ends and the next begins, you need only move one iteration node to be a child of the Current iteration node and move the iteration that just ended to be a child of the Past iteration node.No matter how many “current iteration” queries you have, you only need to edit iteration path I’m glad you asked!In case you don’t believe me, take a look at the pictures below: “Sure, that’s hunky dory for the current state, but we rely on the history for all of our reporting from the warehouse.
Won’t changing the iteration configuration so often make a mess of all that history? The history of the iteration tree is not fully tracked in the warehouse.Scenario: We use a single team project for development of multiple products for multiple different customers.We configure areas and iterations for each different customer/product and set permissions on those nodes to limit access.That being the case, what if we also organize our iterations with Past, Future, and Current nodes?The backlog page structure is created regardless of how deeply nested our iterations path actually is, so an extra level won’t change that behavior.Now our reports can use these dates instead of parsing titles and within Team Web Access these date ranges are used to make iteration planning and reporting more powerful. Without a WIQL variable such as @current Iteration, everyone needs to modify all of their queries every iteration if we want to have any individual or shared queries looking at the current iteration. If you look at the iteration nodes along the left pane of Team Web Access’s backlog page, you’ll note that iterations are grouped according to whether they occurred in the Past, will occur in the Future, or are the Current iteration.