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

1,970 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Lambros VasiliouLambros Vasiliou shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared a merged idea: Allow TFS queries to use shared snippets  ·   · 
    rob gagerob gage shared a merged idea: enable query to look for dates in a sprint  ·   · 
    Alessandro GrapsAlessandro Graps shared a merged idea: TFS: Iteration Path : Get CurrentIteration Path variables in queryes  ·   · 
    Tigran TorosyanTigran Torosyan shared a merged idea: Current Sprint queries Interation Path auto update  ·   · 
    Ramon DurãesRamon Durães shared a merged idea: Add variable @CurrentSprint (WorkItem>Shared Queries>Sprint Backlog )  ·   · 
    stevesteve shared a merged idea: Add @CurrentIteration variable to TFS  ·   · 
    Bryan HintonBryan Hinton shared a merged idea: Add an @CurrentIteration filter to create dynamic work item queries  ·   · 
    AnonymousAnonymous 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  ·   · 

    52 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Kevin AuchKevin Auch commented  ·   ·  Flag as inappropriate

        Hi Jason,

        It is a nice workaround but I would prefer a specific tag for the current iteration.

      • JasonWJasonW commented  ·   ·  Flag as inappropriate

        We use a hierarchical iteration system like this:

        Code\Past\Iteration1
        Code\Past\Iteration2
        Code\Current\Iteraiton3
        Code\Future\Next\Iteration4
        Code\Future\Other

        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)

      • Mitch AguinaldoMitch Aguinaldo commented  ·   ·  Flag as inappropriate

        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.

        Hope this helps.

      • Anonymous commented  ·   ·  Flag as inappropriate

        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.

      • Benny BaggottBenny Baggott commented  ·   ·  Flag as inappropriate

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

      • Anonymous commented  ·   ·  Flag as inappropriate

        Please also consider @CurrentAreaPath as an possible variable for working with queries.

      • Josh HoJosh Ho commented  ·   ·  Flag as inappropriate

        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.

      • Cash FoleyCash Foley commented  ·   ·  Flag as inappropriate

        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!

      • DarcyDarcy commented  ·   ·  Flag as inappropriate

        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

      • DovydasDovydas commented  ·   ·  Flag as inappropriate

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

      • ArjanArjan commented  ·   ·  Flag as inappropriate

        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 RochatNeville Rochat commented  ·   ·  Flag as inappropriate

        Extending this, having the capability of creating queries where work item created dates fall within the current sprint would be welcome

      ← Previous 1 3

      Feedback and Knowledge Base