I'm building a query in ADO and trying to get list of all of the improvement work items with a tag from the last three sprints. Ideally, I want to use this on a dashboard so need it to roll N-3. All the variables I've tried brings back all work items from the last three sprints or nothing. Has anyone else faced a similar issue.
ADO Query
You need to group the clauses. Tick all 3 checkboxes next to Or's for Iteration Path (green in the image below), then click the icon next to And/Or (blue in the image below)
Related
On the Boards section of Azure DevOps, there's a nice filter bar. It contains filters for:
Type
Assigned to
Tags
Iteration
Area
Parent work item
As far as I can see, there's no way to use the section outlined in yellow to filter for work items (for example) created within the last seven days, or due within the next 14 days.
Things I've tried:
Creating a query and viewing results as a board (can't see an option to do that)
Finding a way to script work items into iterations based on date, and then filtering the board based on iteration
Is there a way to do this? It's specifically a board I'd like, as opposed to a Backlog-style list.
Just change the board's settings, Is this what you want?
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.
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.
When, in Azure Devops, opening the Boards > Backlog page there is no possibility to have an overview of all work items accross all of the teams.
You see "All backlogs", but they are divided into the teams.
I want to see an overview of all work items for all these teams.
Is this possible?
You can just create a simple query:
Then you can format it as a flat list or tree.
But keep in mind that the limit for query results is 20000 items.
I want to see an overview of all work items for all these teams.
You can't do that using any of the regular azure boards (kanban board and sprint board).
The only way (well, the only way known to me) to do that is with Queries (Boards -> Queries). To see work items across projects, remember to check the Query across projects checkbox.
At your disposal you have myriads of fields that you can use to filter your results as well. Use them to fine tune your query result if you want. Last but not least, use Column options to specify which columns to show in your result. Since you want work items across projects, you may want to be able to see which project an item belongs to without opening the item. To do that, include the column Area path from Column options dialog. I use the following columns, and sort by ID descending.
Finally save the query.
Now go to Dashboard, click the Edit button, and add the Query Results widget. Configure that widget to use the query you just created. Note that by default, the column Area Path is not included in the Selected columns list on the right, but you have to include it yourself from the Available columns list on the left. Move columns up/down as you see fit.
Click Done editing when you are done. Through that widget you can edit the work items by clicking on the Title of each work item, which will open the item in a modal. You cannot reorder items (I suppose to set priority) on this widget itself, but hey, setting priority is just a few clicks away, so not a big deal. If you like, you can sort the query result using Priority, and after updating priority you should click Refresh to see the updated result.
Hope that helps!
How do I add an existing work item to a the default board?
I can create work items under the Work Items section and I can also create work items by clicking + New Item in the Boards section.
But how can I add an existing item to that board?
I cannot find a setting, field, option anywhere to do that.
This is an organization Azure DevOps.
Your existing item needs to be "visible" to the board by existing in the appropriate iteration path and area path.
Without breaking out all the organization settings that allow you to detail this stuff, the easy way to know the value you need to use is to create a new item on the board you want, and use the values it gets in iteration path and area path on the existing item.
Illustrations:
Make sure your project has areas and iterations that make sense for you. Typically your project will start out with a root iteration path and three child iteration paths:
Iteration 1
Iteration 2
Iteration 3
Iteration paths are used to handle both backlogs and sprints for teams.
The combination of area path and iteration path allows admins to divide sections of the global backlog among the teams that are doing the work.
Think of the connection like a grid. If the rows are iteration paths, then the areas are the columns that divide that row (or vise versa). Multiple teams can operate on the same row (iteration/backlog), but they will only see the work items that also fall inside their assigned columns (areas).
When you create a team the area can be created for you, or you can assign an area to a team after it is created.
You can also change the backlog iteration for a team.
Now your team has a board and a backlog. Again, for your first team, this is done for you.
You have obviously already created some work items, so you'll need to move them into the right area and iteration to make them show up.
This can also be done in bulk from another team backlog
You can configure the board on what to be displayed.
By default, it's the Backlog items, so you will see the work items from your backlog (according to the sprints).
You can't just add a particular work item to the board.
See more details here.