I'm looking to create a query that shows all of the stories that were added to the sprint during our sprint planning meeting. This meeting always takes place on day 1 of the sprint.
Naturally, some stories may be removed mid-sprint but I'd still like to see what was originally planned.
Equally, some stories may be added mid-sprint and I wouldn't want to include those.
I noticed that the built-in Velocity widget has a 'planned' bar, but I'm not entirely sure how that's calculated.
For this issue ,deleted work items cannot be displayed with other work items in queries. If you want to query the stories created by a certain period of time, you can do it in two steps.
First you can query the stories created in the initial time period by the following conditions.
Then you can add the Created Date and Iteration Path column in Recycle Bin to find the stories deleted in this time period.
If your stories are permanently deleted(Remove from Recycle Bin), then you will really cannot query them.
Related
I would like to display the results of a query that identifies the bugs created in the current iteration. AKA "new bugs". I know this can be done by using the created date but that requires the date to manually updated for each new iteration.
Is it possible to leverage the 'current iteration' in the query? Or some way that does require a manual update.
I have tried using only 'current iteration' but this returns all bugs in the current iteration limited by the state that I specify. The result is not limited by when it was created.
I have tried to add a clause for created date, which works, but is not dynamic. meaning it does not increase as the iteration grows in number of days.
Yes, you can add a and/or clause like below
I have a second drop-down list as we have different Teams, so it wants me to tell it which Team I want to bring back items for, from the #CurrentIteration.
I am trying to come up with n Azure Board query to return the work I have performed during current sprint - which I am vaguely defining as:
Work In Current Sprint = [A] + [B]
where
A = work items where I completed development stage (or was decided at some point work is irrelevant) and
B = work items I created in current sprint, not necessarily assign to me nor my team (I spent time investigating an issue, and ended up, for instance, finding a bug, so I want this included in this "report").
The closest I could get is the query blow. Problem is it is still not quite accurate, since with regards to items I created during this sprint - I could not find a way to filter created items in this sprint only - results are showing up work items that CURRENTLY BELONG to current sprint, but not necessarily created in current sprint. The only way I see I can achieve what I want is using CreatedBy - but this only provides a "hardcoded" date range offset, at any given time. If I use an offset of 14 days backwards, running query at the last day of the sprint (considering a 2 week sprint duration) should work, but running the query at any day before that, during the sprint, will return stuff created in previous sprints.
I want this query to help me track "work I have performed during current sprint" (as defined above) at any given day within the sprint.
Any better ideas ?
You could use custom date in 'create date' to limit the work item.
And I notice you use 'work items and direct links', then you need set filters for 'Filters for linked work items' part(as you needed, like iteration path etc.). Otherwise it may return linked work item that belong to other iterations, according to the filled filter, like something belows:
I hope it could help.
We have started our new sprint and in burndown trend ( Azure Devops ) we can not see remaing work in the graph.
At the same time in capacity tab, we can see efforts have been planned for the current iteration.
Are we missing anything.
UPDATE 1
Burn down is based on sum of remaining work and every task has value associated with it. In following image you can see remaining work is 106. But still its not reflected in graph.
Note that on the first day of the sprint there's nothing to burndown. If you hover your mouse over to the far left of the chart, it will highlight the work items that will burndown.
There's also a few different options for the chart. Click through the View the full report to see:
Which backlog are you burning down -- Tasks or Stories? or individual work items?
What are you burning down? Count of work items, Sum of completed work or remaining work?
Note, if you're burning down remaining work your tasks will need remaining work filled out to be useful.
Our teams are using Azure DevOps. We're using the Agile framework and an enterprise release management approach (essentially, SAFe). Our increments are based on the quarters of the year -- for us, this equals 6 sprints.
My goal is to be able to view work scheduled within the current increment as the sprints move along.
I currently have a query that displays current sprint plus the future 5, to give me 3 month's worth of work (see below).
The trouble with this is it has to be edited after each sprint so it only displays the current increment's work. (I have to change it to include the previous sprint and reduce the number of future sprints otherwise it doesn't display completed work in this increment, as well as showing upcoming work from the next increment.)
Increment Planning Query
Sorry for any inconvenience.
I am afraid there is no such increment planning query, that because the value of CurrentIteration will be different due to the change of the current date.
If you want use the #CurrentIteration macros, you have to modify this query after each sprint.
As workaround, you could specify the each Iteration value in the query, like:
With this workaround, we do not need modify the query after each sprint, just need update it after each quarter.
If above workaround not work for you, you could add your request for this feature on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps:
Hope this helps.
I'm creating a view in Azure DevOps for Increment Planning. I want to display all Features that have scheduled work for the next 6 sprints. The Feature might not be scheduled to complete in that time, but one or more User Stories are.
I want to create a Feature/User Story tree view with items displayed as follows:
All Features whose iteration path is within the next 6 sprints, with User Stories under them, in tree view.
All Features that have a User Story within them whose iteration path is within the next 6 sprints, in tree view.
In practical terms, it should:
Display any Feature that has an iteration path of 1908-2, 1909-1, 1909-2, 1910-1, 1910-2, 1911-1 regardless of if it has User Stories under it.
And it should display any User Story that has an iteration path of 1908-2, 1909-1, 1909-2, 1910-1, 1910-2, 1911-1 under its Feature (regardless of the iteration path of the Feature).
So a Feature with an iteration path of 1911-2 or anywhere in the future (such as 2006-02) should display, IF it has a User Story with an iteration path of 1908-2, 1909-1, 1909-2, 1910-1, 1910-2 or 1911-1.
I've been able to write a query that returns all Features (and their Stories) within iterations 0-5, but this doesn't return any Features outside of this range if they have Stories that are within the range.
Here's the query: Features > Iterations 0-5 > User Stories as Child
And the results: Obviously, just Features within Iterations 0-5
The problem is, there are Features (like this one) that have User Stories within the increment that aren't being returned, because the Feature's iteration isn't within range, even though the User Stories are.
Here's a query that returns all Features and only User Stories within iterations 0-5:
As you can see, this returns Features (with no User Stories) outside of this range:
I need to see ALL work that is scheduled to be completed over the next 6 sprints, in a Feature/User Story tree view. If I were able to use If/Then, I don't see this being a problem. But I'm having a very hard time figuring it out with And/Or...
I was able to resolve this by using the State in the query. A Feature won't have User Stories under it unless it is Active. So, by filtering out New and items that are in the Backlog, it results in all work.
I expanded my query to include Scenarios and here is what it looks like: