I suggest you ...

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

TeamProject=@Project
And WorkItemType In Task,Bug
And State in New,Active
And IterationPath Under @Project\Current
And...

It would be really good to be able to write this basic query "All active bugs and tasks in current iteration" and then just "include" it in derived queries (e.g. base + "and AssignedTo=JoeBloggs")

Having just discovered a bug in one such query, and spent hours "copying and pasting" the core query into all the variations, this would have been a massive time-saver.

rob gage
shared a merged idea:
enable query to look for dates in a sprint · May 13, 2014 ·

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

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!

Anonymous
shared a merged idea:
TFS Current Sprint Macro for query builder: if i have an Iteration tree like ProjectName -> Sprint Number -> Sprint 80 -> Reports. I would · Jan 10, 2012 ·

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.

Whoo hoo!!! (I'm generally pretty reserved, so you can take this as awesome news.) T/his has been an annoying soft spot in the product and will save me from the manual Sprint/Iteration "dance" that I never got around to automating)

You can then query a specific iteration, and anything in the "groups: current, next past and future.
At the end of the iteration, you just drag Iteration3 into "Past" and it magically moves everything in that iteration to the "past" group (without adding any history to all the hundreds of individual items)

I think I read through 1/2 of the comments, so I don't know if someone already suggested this, but our work around was to create a sprint literally called "current sprint." At the close of each sprint, we'd then move all the items under the "current sprint" iteration into a more aptly named sprint iteration (eg Sprint# YYYY-MM-DD to YYYY-MM-DD) and move everything for (sprint + 1) into the current sprint. Our PM's are given two folders worth of queries, 1 that only points to "current sprint" and then copies that they're allowed to change the sprint.

To update iterations en masse, we're currently just exporting everything into excel and doing a copy/paste/update. I should note that we are currently only rolled out to a handful of teams with an average of <5 resources/team. I can see this not working for people following the 1 collection per enterprise model, but a solution for another time I suppose.

Our request is along the same lines. We would like to use the dates of the current iteration to exclude work items from the forecast list. This is one of the most powerful backlog grooming tools in TFS 2013, but now it includes all New and Active work items in the current sprint, counting the story points for the New items and just listing but not counting the story points for the Active work items. It makes the tool impossible to use as intended.

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...

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.

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!