15 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Jonathan commented  ·  April 17, 2013 11:33 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Is the change done yet ? It was more than a year ago now...

• Alex Scott commented  ·  March 21, 2013 10:31 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  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.

• wesley commented  ·  February 28, 2013 10:59 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  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  ·  January 15, 2013 1:47 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Here's one suggestion for this issue:
  http://intellitechture.com/transitioning-between-sprintsiterations-with-tfs/

• Stephen Hewison commented  ·  January 7, 2013 10:16 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Definitely needed. It makes current iteration reporting useless without it.

• Malosh commented  ·  January 3, 2013 1:18 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  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)?

• Dan commented  ·  November 14, 2012 5:04 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I like current token, would save me from editing the query every week.

• Alex commented  ·  October 9, 2012 2:23 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Having iteration start and end dates available for query and as a column option would be massively beneficial.

• Terry Short commented  ·  June 27, 2012 1:50 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I also would prefer an explicit Current Interration/Sprint that the Scrum team/master sets and all the current sprint queries can then use that.

• Phil Spokas commented  ·  June 21, 2012 2:57 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I recommend *not* having TFS calculate this automatically, but rather the Scrum team/Scrum Master make an explicit declaration about which sprint is *current* and exactly when. There's too much variability in real life over when the current sprint is actually current at sprint transition and planning time.

• techSage commented  ·  June 3, 2012 5:46 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  It seems that it shouldn't be terribly hard to do since the Team Project Dashboard shows the Current Iteration. Use that code wherever the system variables like @Project are created. Of course, I'm probably drastically oversimplifying this since I know nothing about how VS is developed.

• Anonymous commented  ·  April 10, 2012 1:35 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  A useful important thing also would be a query variable like @CurrentIteration for workitem queries. In my opinion for Scrum a minimal requirement.

• wheelswiemann commented  ·  March 28, 2012 4:44 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  This feature would be very beneficial, especially when you look at the opportunities for leveraging the dashboard type views on a project portal.

• Andy Bray commented  ·  January 22, 2012 9:39 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Agree - this would save having to update all of the 'current sprint' queries every couple of weeks which is a bit clunky.

• AdminVisual Studio team (Product Team, Microsoft) commented  ·  January 11, 2012 1:49 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Thanks for your suggestion.

  We have heard this feedback more often, and is something we would really love to do. We had to make the tough decision to put it below the cut line when we compare it to the other work we need to get done for Dev11.

  But it is definitely something we consider for the future.

  Ewald Hofman (TFS Program Manager)