VSO Support @currentIteration+-1 for next or past iteration
currently there is no way to identify next iteration and Past iteraton. ideally we assume @currentIteration +-1 should work.
Use case: 1.We need our user stories to be approved for next iteration, before we start work. Now as VSo just support @currentItertion, we need to manually update our query every 2 week.
2. Once iteration is over, we performed iteration review, again we have to manually change the query(@currentIteraton-1) or something generic to achive the same will be too useful
We have been wanting to tackle this item for awhile, but it was always cut in favor of other priorities and due to the cost associated with changes to our Work Item Query Language (WIQL).
However, we recently prototyped a WIQL macro improvement and started work to implement the full fledged solution, which will be rolling out soon (within the next 2 – 3 weeks). Once it hits your account, you will be able to query for items using @CurrentIteration +/- N as your syntax so that you are not limited to only the immediate future and previous iterations.
Thank you for your patience on this feedback item. We will update to “complete” once the functionality has been enabled for all VSTS accounts and include a link to further details about how to use the new offset functionality.
Andy Bevan commented
So exciting!!!! Thank you!
In the 70 or so comments on the topic already, has no one from VSTS dev team responded or commented on it? @FutureIteration, @PastIteration, @CurrentIteration -N/+N would be most helpful.
Dustin Woodhouse commented
ETA for this? +1 for @NextIteration and @PreviousIteration.
Marius Strom commented
Would really love to query Iteration Path < @currentiteration to find things assigned to iterations before the current one..
Fred Bhesania commented
+1 for @previousIteration and if possible, ability to do -n where iterations are symmetric,
Lars Ruoff commented
+1 for @NextIteration and @PreviousIteration.
Michael Taylor commented
I would love this feature as well but the problem is that @currentIteration + 1 is not a value that can be determined unless you put restrictions on how iterations are defined. You might name your iterations Sprint 1, Sprint 2, Sprint 3, etc but others don't . We use a 2 digit values that resets each year. There is no reliable algorithm that could determine iteration + 1.
You could argue that it should be date based, and that would probably be the better option. But iterations can overlap within the same project. Iterations may not even have dates (backlogs, for example).
I would like to see this feature implemented but I think the rules of last, next should be defined first.
This would be a very valuable feature to deliver
Is this feature available yet? This shouldn't be that hard to deliver..
Russ Rolfe commented
I would like to add my voice to saying I would like to also see this. In the mean time is there a work around
Camila Salaberry Paula commented
I would like to have this feature available soon. Please it is important to build reports.
Dan Jones commented
Would love the -1 for retrospectives and the +1 for sprint planning.
Feature is @overdue + 1
Currently, there is no easy way to view the current iteration and past iteration
Sonya Kotov commented
Don't stop at @currentIteration+1 - supporting @currentIteration + 2,3, maybe 4 would be nearly as easy and super useful!
Michael Mainer commented
This would help my beginning of month workflow to determine what didn't happen last month.
Would very much use this. Would also love to be able to say "all past iterations" as an include/exclude query option. Or "all future iterations."