Creating Queries - Token for Current Iteration
When creating a work item query, you are given the option to select the iteration path for which the query is to return results for. It will be fantastic if a token was provided such as [Active Iteration] and you can specify the active iteration manually, or TFS calculating it via the Start/End dates
When Sprint N finished and started Sprint N+1 we have to update all queries manually. It will be nice to have "Active Iteration Query" type or some kind of alternative.
Simplifying the user experience
Add @CurrentIteration variable to TFS so your team queries know which teh current sprint is like @Project or @Me
Since we can detect what the current iteration is for a team - it would be nice to be able to build work item queries that continually changed as the iteration changed - an @CurrentIteration filter would be fantastic!
TFS Current Sprint Macro for query builder:
If i have an Iteration tree like
ProjectName -> Sprint Number -> Sprint 80 -> Reports
I would a macro that allows all queries to change sprint automatically.
ProjectName -> Sprint Number -> "CurrentSprint" -> Reports
A potential workaround for some, especially those using the scrum template is to edit your 'current' query to only display the active items. For instance with the scrum template, only show the items where the state = committed. If you're using scrum, are you actually working on new, approved or done stories?
And there doesn't seem to be a need to even change the iteration paths anymore since the stories show up in the backlog if the iterations have dates. I think having a child task where the iteration s set also makes the story show up in that iteration as well.
Marco Medrano commented
Please add also this feature to TFS online.
How about now? The community is desperate asking for this functionality, but this wish seems to be under review but nothing happened for the last 2 years ?
Keenan True commented
As mentioned, it seems somewhat ridiculous that this doesn't exist and is taking this long when the functionality already exists in a non-query form on the Work -> Backlog tab.
Can this please be released into a path for TFS 2012?
John Foster commented
I'd be even happier with a [Previous Iteration] option. Seriously, I currently can only query <> iteration? Microsoft does a lot of stuff great, but it is the little things like this that brings it down the the level of their competition.
FYI; not giving this a vote as this one covers the same and has much more votes: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2293180-creating-queries-token-for-current-iteration
Totally agree. This has been asked for since TFS 2010. Unfortunately it's still not there. Looks like a simple thing and making a lot of us happy.
Totally agree. This has been asked for since TFS 2010. Unfortunately it's still not there.
Mandrado Silva dos Santos commented
We look forward by this feature, we use the process template scrum and we have many Team Projects, with several areas of work and many sprints, so we have many queries to change every sprint, with this feature would not have more of this work.
Jerry Valle commented
Any update on this for this year or next?
for initial release of TFS 2013, is there any hope for getting this? (still not on latest web version with the 2013 bits)
@Current as an iteration path? That would be nice.
Is the change done yet ? It was more than a year ago now...
Alex Scott commented
If you change your iteration path from Sprint 1 to Current, all items in Sprint 1 will automatically move to Current. When you rename Current back to Sprint 1, all items are moved back into Sprint 1 and you are now ready to rename Sprint 2 to Current. Works great when you manage sprints in the iteration path. All your current sprint queries never have to change from /Current. We moved away from managing our sprints in the iteration path and now we realize we traded one set of problems for another.
On January 11, 2012 11:49 p.m Visual Studio team (Product Team, Microsoft) wrote: "We have heard this feedback more often, and is something we would really love to do."
415 days ago.
Lambros Vasiliou shared this idea · Oct 4, 2011
514 days ago.
How can the Visual Studio Team release a feature with such a flawed design?
I think we need a uservoice "idea" to improve uservoice satisfaction. If we create it today we might get satisfaction in 600 days.
Stu Miller commented
Here's one suggestion for this issue:
Stephen Hewison commented
Definitely needed. It makes current iteration reporting useless without it.
Adding a new Field such as "Query Name" (or "Query") can alternatively resolve the need for defining new tokens.
For example: I would manually edit a Query named 'Active Iteration' periodically, while having in multiple Queries a Clause with Field set to "Query", Operator set to "Satisfied" and Value set (from a drop-down list) to "Team Queries\Current Sprint\Active Iteration".
I think such feature would increase the Query flexibility significantly, and maybe simpler for implementation (than user-defined tokens)?
I like current token, would save me from editing the query every week.
Having iteration start and end dates available for query and as a column option would be massively beneficial.