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
We often look at the backlog when doing quality checks and audits for work created or amended within an iteration.
When using the query editor, the only options on a date or datetime field when using the operator In is today -x days
Could we have for all date fields an option to select In then an iteration path and have the query return all matches where the date of the field being searched is within the start and end dates of the iteration
Why will you insert the possibility to Get the current Iteration Path in query filter: like TFS @CurrentIteration
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
Benny Baggott commented
I'd settle for knowing how to write a script that would automatically go and update all of my queries from one iteration to the next. Can anyone tell me how to do that until someone at Microsoft figures out what we have known for years? I am having to manually change over 20 shared queries each sprint. And don't get me started as to why I can't do the "Current" iteration trick or get the Scrum Masters to all change their own shared queries...
Please also consider @CurrentAreaPath as an possible variable for working with queries.
Joseph Ville commented
Please implement this feature! It would greatly improve project efficiency.
Josh Ho commented
I really would like to see this functionality. From the looks of it...Microsoft is no longer reviewing User Voice ideas...or at least they aren't updating the community submitted ideas with any feedback.
Then I would link it from any documentation portal, for instance: http://hostname:8080/tfs/CompanyName/_backlogs/Iteration/ProductName/Current
Absolutely agreed. This is a necessity.
Cash Foley commented
This needs to be "Team Context". Having multiple teams in a single project is great except having different Shared Queries for each is a pain. Putting this configuration on a Team level will allow Shared queries to act in the context of the team!
Shaunt Kojabashian commented
yes please.... definitely want this feature.
This isn't actually as simple as people might think. Remember that the TFS Work items are shared across teams, and so are the queries, but he Iterations that are applicable are controlled team by team, so the best you could probably do is "part of ANY active iteration", because you DO want the results of the query to be consistent for each team
Don't get me wrong, I still think it would be hugely helpful. There IS an answer and we should have this by now, but it's not as simple as a @CurrentIteration token
The best workaround I have found is to have my iterations organized with parents for "Past", "Current" and "Future", and then at the start of every sprint I simply drag and drop the last sprint into the "Past" bucket and drag then next sprint into the "Current".
If you do this, you can write queries like "Iteration Path UNDER Whatever\Current\" and it'll always point to your current iteration
Guys, seriously. It shouldn't be that hard. If you are having trouble integrating this for almost 3 years we can even code it for you if you want...
2,5 years later now, VS11 has already been shipped. Visual Studio 2013 is even shipped. Still not able to use the active iteration. And it was a tough decision to release this feature after VS11?
Neville Rochat commented
Extending this, having the capability of creating queries where work item created dates fall within the current sprint would be welcome
Peter Hunter commented
It would be nice to have an @CurrentSprint macro to set to when filtering on Iteration Path
Yes this would be hugely valuable, please ...
Adding new [Token] takes MS years commented
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."
Hurry this up.
What' the level of effort on this, 1 day? It would make everyone's life so much easier.
This would be very useful for our Company as we have many users that would wish to write their own queries that they would reuse from iteration to iteration and having to change the iteration value each time would be a pain.
The feature to have a wild card filter for the current sprint would be very useful to my company. I look forward to the update that includes it. Many of the planning query we use have to be update as we move from one sprint and iteration to the other an have the ability to set the current sprint as a filter in the query would remove this error prone approach and maintenance issue.
Please add this, we need this - not sure why there is so much resistance to it. Its a no-brainer, why wouldn't I want my current iteration/sprint query to have a wildcard for "current iteration"? You obviously have the token already, or I wouldn't be able to set it in the admin area!
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.