Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
On User Voice there is a request to be able to query on the current iteration. We have it on our backlog, but it won't ship it for Dev11.
However there is a workaround, found by Mark Michaelis, that you can use to avoid having to update all your work item queries if the team moves to the next sprint.
The idea of the workaround is the following
Thanks Mark for being so creative.
Thanks Mark and Ewald for the post....Btw Happy Birthday Ewald!!!
While not focused on the backlog item i.t.o. being able to query, Mattias Sköld released an extension at visualstudiogallery.msdn.microsoft.com/c597fa72-1f09-4d3c-a98a-b190fe5abd68 which helps you with the creation of new iterations, change of the current iteration and automatic update of team queries when changing the sprint.
Ewald, hoping that you are having a phenomenal birthday :)
Does TFS 2013 address this issue?
Sorry this has not made it to the cut of TFS 2013.
It is still high on our backlog, and we are considering it for one of our next releases.
Did this make it into TFS 2013 Update 2?
Nice workaround. Thanks!
So, any update on this getting into a future version?
Any news when this could be implemented?
It is a very basic feature that everyone needs to. WTF Micrsofot. Do release it soon.
I am happy to announce that we have released the support for @CurrentIteration today to Visual Studio Online. If you have an on-prem instance of TFS, it will be first available in TFS 2015 RTM.