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,096 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 →
    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  ·   · 

    31 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...
      • techiejohntechiejohn commented  ·   ·  Flag as inappropriate

        What' the level of effort on this, 1 day? It would make everyone's life so much easier.

      • Anonymous commented  ·   ·  Flag as inappropriate

        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.

      • PhilipPhilip commented  ·   ·  Flag as inappropriate

        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.

      • SteveSteve commented  ·   ·  Flag as inappropriate

        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!

      • shamusshamus commented  ·   ·  Flag as inappropriate

        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.

      • Anonymous commented  ·   ·  Flag as inappropriate

        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 TrueKeenan True commented  ·   ·  Flag as inappropriate

        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 FosterJohn Foster commented  ·   ·  Flag as inappropriate

        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.

      • Luc van VugtLuc van Vugt commented  ·   ·  Flag as inappropriate

        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.

      • Mandrado Silva dos SantosMandrado Silva dos Santos commented  ·   ·  Flag as inappropriate

        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.

      • FelickzFelickz commented  ·   ·  Flag as inappropriate

        for initial release of TFS 2013, is there any hope for getting this? (still not on latest web version with the 2013 bits)

      • Alex ScottAlex Scott commented  ·   ·  Flag as inappropriate

        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.

      • wesleywesley commented  ·   ·  Flag as inappropriate

        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.

      ← Previous 1

      Feedback and Knowledge Base